> Do we really need to test our code on 50ish Chrome versions, 25is Firefox versions and so on. Probably not, unless you're a really big outfit with a vast user base. But you should test on at least a recent Chrome version and a recent Firefox version, and probably Safari. And unless your product is irrelevant to mobile users, on both iOS (Safari) and Android (Chrome, Firefox), with both phone and tablet form factors…
Painful as it is to admit, even Firefox is not worth testing. In our B2B site, more people are using IE11 than FF. https://gs.statcounter.com/browser-market-share at ~3% of overall share / 7% desktop-only share it's hard to justify putting extra effort.
Ask HN: How relevant is cross-browser testing anymore?
21–30 of 97 posts
Re: Ask HN: How relevant is cross-browser testing anymore?
#22Re: Ask HN: How relevant is cross-browser testing anymore?
#23I have no idea about how relevant it is, but every few months I see a website which seem to be tested in Chrome only, because it blatantly don't load in Firefox or Safari. Like, at all, blank page. Or have some buttons like "Purchase" not working.
Re: Ask HN: How relevant is cross-browser testing anymore?
#24Also please consider writing your apps in a way such that they don’t completely shit the bed if your 600th ad tracker script fails to load. I hate having to disable pihole so that Google can track me while I pay my utility bill.
Re: Ask HN: How relevant is cross-browser testing anymore?
#25Please test with Safari on desktop at least. I routinely find things that are just completely broken. And not small names, big names like Hulu, Clover, green chef, and others have just completely broken on Safari. Integration with Google’s captcha seems to be a common failure point. Also please consider writing your apps in a way such that they don’t completely shit the bed if your 600th ad tracker script fails to lo…
I can't see why anyone would still use it today when FireFox for Mac has become so good.
Re: Ask HN: How relevant is cross-browser testing anymore?
#26Please test with Safari on desktop at least. I routinely find things that are just completely broken. And not small names, big names like Hulu, Clover, green chef, and others have just completely broken on Safari. Integration with Google’s captcha seems to be a common failure point. Also please consider writing your apps in a way such that they don’t completely shit the bed if your 600th ad tracker script fails to lo…
Re: Ask HN: How relevant is cross-browser testing anymore?
#27> Do we really need to test our code on 50ish Chrome versions, 25is Firefox versions and so on. Probably not, unless you're a really big outfit with a vast user base. But you should test on at least a recent Chrome version and a recent Firefox version, and probably Safari. And unless your product is irrelevant to mobile users, on both iOS (Safari) and Android (Chrome, Firefox), with both phone and tablet form factors…
Painful as it is to admit, even Firefox is not worth testing. In our B2B site, more people are using IE11 than FF. https://gs.statcounter.com/browser-market-share at ~3% of overall share / 7% desktop-only share it's hard to justify putting extra effort.
(Test IE11 as well, by all means, if it's relevant to your users; but it's much less relevant to the future of the web.)
Re: Ask HN: How relevant is cross-browser testing anymore?
#28Feels like everything just works on Chrome and Firefox, but Safari is the new IE.
Re: Ask HN: How relevant is cross-browser testing anymore?
#29I have noticed that there are still vast differences in the printing functionality, both in terms of how things render and performance. So if you need to do any kind of printing in the app and you know your clients will use an array of different browsers it is worth checking it. Even within the same browser things tend to go back and forth when it comes to printing, Chrome for example tends to break things in one ver…
Re: Ask HN: How relevant is cross-browser testing anymore?
#30> Do we really need to test our code on 50ish Chrome versions, 25is Firefox versions and so on. Probably not, unless you're a really big outfit with a vast user base. But you should test on at least a recent Chrome version and a recent Firefox version, and probably Safari. And unless your product is irrelevant to mobile users, on both iOS (Safari) and Android (Chrome, Firefox), with both phone and tablet form factors…
Painful as it is to admit, even Firefox is not worth testing. In our B2B site, more people are using IE11 than FF. https://gs.statcounter.com/browser-market-share at ~3% of overall share / 7% desktop-only share it's hard to justify putting extra effort.
(Disclosure: I am still very much a Firefox user, so this might be projection.)