Once it's done, everything is nice and snappy, but it's like a 20-30 second wait after the wire even on my beefy 5900x. We failed to anticipate just how large some of the templates clients would be making, so sometimes when they open a template they end up having a couple hundred of these editors hidden behind drag and drop enabled accordions.įirefox chokes on the initial TinyMCE calls for these large templates, taking quite a long time to fully render the page. I went with it because I was able to implement it in an afternoon, their licensing was compatible with our use, and I had a tight deadline. For writing steps and substeps, I use a WYSIWYG HTML editor called TynyMCE. I have a web app that allows customers to make templates for their standard operating procedures that they pull from our main product. But I still think it has some catching up to do with Chrome. It is my primary browser for both development and personal use. I've been shilling for Firefox for years.
0 kommentar(er)
