4 ms·

I don't think it's worth testing on old versions of Chrome and Firefox since they're updated automatically. iOS Safari on the other hand, can't be updated on o

I don't think it's worth testing on old versions of Chrome and Firefox since they're updated automatically. iOS Safari on the other hand, can't be updated on older phones since it's tied to iOS updates. This makes any Safari bug linger for a few years. It's also the only rendering engine available on iphone so some people are truly stuck using an old version. So I'd say, test on Chrome because it's ubiquitous and test on iOS Safari like it's the new Internet Explorer. I'm not sure about Firefox. I personally use it and test on it, I think it's the right thing to do for the web. And at least with that you've covered most rendering engines.

justsomehnguy 4y ago
> I don't think it's worth testing on old versions of Chrome and Firefox since they're updated automatically https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle https://support.mozilla.org/en-US/kb/firefox-esr-release-cyc...
s1mon 4y ago
I don't disagree that most versions/instances of Chrome are updated regularly, but implying that this is universal is questionable. Chrome is only updated if the user lets it happen. I can't count the number of times I've watched some co-worker share their screen on a conference call and the Chrome update button is lit up, but apparently that's not a trigger to these people (I update pretty much as soon as I notice the indication since Google has done a remarkably good join of updating in place in a way that most SaaS things and web sites just reopen without trouble). I'm sure the next time they restart/reboot it will get updated, but if there was some hideous Chrome-related bug which is from a release a month ago, you might want to think about that. It's also entirely possible to turn off updates if you or some misguided IT person is really so inclined.
- dutchCourage 4y ago
  Good point, it's definitely not universal. Maybe it's more fair to think of it in terms of priority. I don't expect a smaller team to test on many versions, but the bigger the team and the more users they have, the more diligent they should be with their testing. So in my opinion, in order, I'd test on: - current Chrome - current Safari - older Safari - older Chrome & current Firefox Not sure what comes next, IE 11 maybe? I guess at some point it's good to look into automating some testing. And it's worth noting, as with most things, that "it depends", I don't expect the same browser support from something like Figma and from a government website for example.

justsomehnguy 4y ago

> I don't think it's worth testing on old versions of Chrome and Firefox since they're updated automatically https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle https://support.mozilla.org/en-US/kb/firefox-esr-release-cyc...

s1mon 4y ago

I don't disagree that most versions/instances of Chrome are updated regularly, but implying that this is universal is questionable. Chrome is only updated if the user lets it happen. I can't count the number of times I've watched some co-worker share their screen on a conference call and the Chrome update button is lit up, but apparently that's not a trigger to these people (I update pretty much as soon as I notice the indication since Google has done a remarkably good join of updating in place in a way that most SaaS things and web sites just reopen without trouble). I'm sure the next time they restart/reboot it will get updated, but if there was some hideous Chrome-related bug which is from a release a month ago, you might want to think about that. It's also entirely possible to turn off updates if you or some misguided IT person is really so inclined.

dutchCourage 4y ago
Good point, it's definitely not universal. Maybe it's more fair to think of it in terms of priority. I don't expect a smaller team to test on many versions, but the bigger the team and the more users they have, the more diligent they should be with their testing. So in my opinion, in order, I'd test on: - current Chrome - current Safari - older Safari - older Chrome & current Firefox Not sure what comes next, IE 11 maybe? I guess at some point it's good to look into automating some testing. And it's worth noting, as with most things, that "it depends", I don't expect the same browser support from something like Figma and from a government website for example.