4 ms·
So now assume they test and find it doesn't work on mobile Firefox. What should they do? Refrain from rolling out the design to Chrome and Safari until Firefox
by fixermark 9y ago
So now assume they test and find it doesn't work on mobile Firefox. What should they do? Refrain from rolling out the design to Chrome and Safari until Firefox performance catches up, or roll out the functionality differently on different browsers?
Sounds like, based on the descriptions here, they're doing the latter, right? Infinite scrolling on Chrome vs. paged viewing on Firefox, for instance.
- kuschku 9y agoThey’ve now had 4 years. 4 goddamn years to update the Firefox version, and they’ve just removed features instead.
- fixermark 9y agoThat sounds like it was unworkable in Firefox. Maybe FF just isn't a very good browser? You can be standards-compliant while implementing the standards with performance problems and ugly corner-cases.
- kuschku 9y agoIt works in Firefox. Always has. Change the UA, and it just works. This is the same story as when Google made Inbox a "Chrome-Exclusive" that also didn’t run in Safari, Opera, or even fucking Chromium. It’s just anticompetitiveness.
- IncRnd 9y ago> It’s just anticompetitiveness. I find it interesting how a word's proper usage is in a case that it's opposite would work better! Anticompetitive is the right word in your sentence, of course, but google isn't anti-competitive in this case with firefox. It is ultra-competitive!
- s73ver 9y ago"So now assume they test and find it doesn't work on mobile Firefox. What should they do?" Fix it, just like any other website out there.