There were also two interview participants who said they didn’t have the hardware for testing Safari. (Not transcribed.)
Breaking changes Although breaking changes, or regressions, was not among the overall top pain points , and are not always cross-browser compatibility issues, we have clear feedback from the survey and interviews worth highlighting. Note for web developers: How to file a good browser bug is a good resource for how to report that a regression has happened. If the problem is reported early, the chances of the change being reverted are better. Web developer quotes In the survey’s free-form comments, there were several comments about testing and not having access to the necessary hardware: Breaking changes are not uncommon. Particularly for Chrome, where unannounced behavior changes are often introduced. Frequent browser updates (especially Chrome / Firefox) that potentially change browser behaviour.
Chrome changes (including mDNS with WebRTC) quietly
Things that used to work suddenly stop because of browser updates. This unstability places an unfair maintenance burden on the developers, wasting time and money.
Bugs introduced by browsers (so, a feature that was working fine now doesn't work) that takes ages to get fixed again.
One interview participant also told us about seeming regression in iOS 13:
In our CMS we have input fields using CodeMirror […] with iOS 13 there have been a lot of changes, under the hood, probably. Because cursor placement, copying and pasting inside of CodeMirror no longer works reliably. Text selection is broken. I don’t know if it’s a CSS issue on our side, but my guess is it’s mostly related to something in iOS that’s changed. […]
Made with FlippingBook - professional solution for displaying marketing and sales documents online