3 ms·
Sadly, my case is the opposite. I use Firefox since the beginning so it is close to 20 years. I'm not going to use it as my main browser anymore as I'm working
by meiraleal 3y ago
Sadly, my case is the opposite. I use Firefox since the beginning so it is close to 20 years. I'm not going to use it as my main browser anymore as I'm working fulltime with PWAs and service workers and Firefox support of it (or lack of) is unjustifiable.
My new apps make use of modern HTML and JS APIs and I can't count on Firefox implementing them.
- toyg 3y ago"Modern HTML and JS APIs" were designed by Chrome for Chrome, so unsurprisingly work better on Chrome.
- meiraleal 3y agoAnd Firefox solution is to ignore all developers that think this is a great platform compared to Play Store and App Store. Great way to lose market share.
- lucasyvas 3y agoI think you're justified in this case - this isn't about not supporting Chrome or the features it offers, just saying that it has some issues that make it not great as a browser for many end-users. This is one such case that hopefully has a resolution. But, as for any platform, I think it's fair to take advantage of additional things one platform gives you over the other. That's so long as you properly support the others still.
- sam_goody 3y agoI use lots of modern APIs and CSS (on our own site) with no issues. I can only remember one site in the past month that had an issue in FF, and it was probably because of user agent checking. What API's are you referring to, and where did you come across them?