[ozim]

I tried FF dev edition with Angular, it was getting randomly slow. Weird issues popping while debuging typescript code. In the end I have to use Chrome for my work, even though I would like to drop Chrome personaly. That said, I sometimes have to debug Angular applications on IE11 which is worst nightmare...

[ktpsns]

I had similar experiences with a Vuejs application where I rendered thousands of "reactive" elements. The Chromium JS engine had substantially better performance then the Firefox JS engine.

However, to be fair, this is a strong sign that as a developer, we are doing something wrong. If a JS application feels slow on an average browser in an average computer, it will feel slow on all slower computers. The usability will be crap. In this particular example, the frameworks are not suitable for such a large number of "reactive" elements.

[giancarlostoro]

If its having performance issues on Firefox.... Leaving Firefox and making it work on Chrome is part of the problem with the browser wars... I also would consider that a bug in either that framework or your code or both. I rather websites worked the same in all browsers otherwise why bother with JS frameworks that are to be compiled for all browsers.

[angrygoat]

I use Firefox developer edition as my main browser, and there does seem to be some issue with Angular sites. admin.google.com is particularly bad – but so bad it makes me wonder if they only test in Chrome.

[eitland]

Error logging used to be broken in Firefox at least until last year. I'm not working in frontend at moment and I never got around to submitting a bug (it always happened while at work) but my opinion was that there was a bug somewhere in there where they used a Chromium only API.

And yes, I too have wondered if they only test in Chrome.