4 ms·
Why is poor performance in one browser a reason to completely drop support for that browser? If it works correctly albeit slowly, why not support it anyway? The
by AshleysBrain 12y ago
Why is poor performance in one browser a reason to completely drop support for that browser? If it works correctly albeit slowly, why not support it anyway? Then the slow experience is motivation for the browser vendor to improve it as well.
- JshWright 12y agoBecause users aren't going to blame the browser vendor for the poor experience?
- Touche 12y agoUsers won't get to use the site at all.
- jamesgeck0 12y agoYou can spoof the user agent in Firefox and see for yourself. It's _really bad_, bordering on completely unusable (at least, it was at launch). Inbox uses a lot of animation, and having that animation run at a couple frames per second makes an exceptionally poor user experience. If I worked on Inbox, I wouldn't feel comfortable releasing anything like that on Firefox either, even if it was gated with a disclaimer. It wouldn't reflect well on Google or Mozilla.
- dblohm7 12y agoThat would require them to file bugs against the browser. In the case of the sparse array issue, nobody had filed anything until a Mozillian read about the issue here on HN. It was fixed in Nightly the same day.