3 ms·

Same here. We just kept running into bugs with Firefox, especially with a lot of "newer" technologies like WebRTC. It hurt to deprecate because I used to be su

Same here. We just kept running into bugs with Firefox, especially with a lot of "newer" technologies like WebRTC. It hurt to deprecate because I used to be such a Firefox fanboy. The last few years there's been a compounding effect of Chromium/Blink adding features that aren't supported elsewhere and Firefox just having a slew of very outdated bugs that haven't been fixed for years that have made it difficult to use. The percentage of our users who use Firefox has also steadily declined... most likely because we have to throw up "Unsupported browser, things may not work" warnings all over the place because the number of random bugs users keep running into.

BeefWellington 4y ago
I'm curious as to what these specific issues you guys are mentioning are. I browse the web largely with a Chrome UA string on Firefox and I don't think I've ever seen an actual problem. If I don't use a Chrome user agent though, I get a lot of "This site will only work in Chrome/Edge" or "This site doesn't work in Firefox" popup nonsense, which is especially funny when the sites function otherwise completely fine.
- solardev 4y ago
  The same Canvas code runs fine on Webkit and Blink, but really really slow on certain Firefox builds (dependent on OS and CPU architecture). I'm not at work and don't have the bookmarks handy, but you can search their issue tracker and see dozens of open issues along those lines, stretching back more than 5 years and still unresolved. I'm sure Firefox works fine for most sites, but if you're one of those that it has an issue with, well... just like IE, below a certain % of usage share, we just have to make the decision to not support it. Actually, this was a learning experience that caused one of our devs to switch from Firefox to Chrome too. We didn't realize how far behind Firefox had gotten until we had to debug the issue and read through their tracker. Mozilla just ignored the threads after a while and they kept building and building. We haven't put up a warning banner yet but probably should. It's like IE all over again lol.

BeefWellington 4y ago

I'm curious as to what these specific issues you guys are mentioning are. I browse the web largely with a Chrome UA string on Firefox and I don't think I've ever seen an actual problem. If I don't use a Chrome user agent though, I get a lot of "This site will only work in Chrome/Edge" or "This site doesn't work in Firefox" popup nonsense, which is especially funny when the sites function otherwise completely fine.

solardev 4y ago
The same Canvas code runs fine on Webkit and Blink, but really really slow on certain Firefox builds (dependent on OS and CPU architecture). I'm not at work and don't have the bookmarks handy, but you can search their issue tracker and see dozens of open issues along those lines, stretching back more than 5 years and still unresolved. I'm sure Firefox works fine for most sites, but if you're one of those that it has an issue with, well... just like IE, below a certain % of usage share, we just have to make the decision to not support it. Actually, this was a learning experience that caused one of our devs to switch from Firefox to Chrome too. We didn't realize how far behind Firefox had gotten until we had to debug the issue and read through their tracker. Mozilla just ignored the threads after a while and they kept building and building. We haven't put up a warning banner yet but probably should. It's like IE all over again lol.