First of all thank you for relativising my one-sided comment. Let me clarify what I mean a bit. I agree with you on your arguments about Chrome. I don't suppor

First of all thank you for relativising my one-sided comment. Let me clarify what I mean a bit. I agree with you on your arguments about Chrome. I don't support Chrome specific features. They even have broken things in the past. My perspective on this is that iOS locks out non-Safari browsers, so users are forced to use it and as a developer I'm forced to make workarounds for it. With IE11 I don't have this problem anymore. We're at a stage now where I can convince my clients of "This is a browser, which is losing official support soon. I can make this feature work/look better on IE11 if you really want, which costs me this much time". IE is being faded out just by the fact that more new stuff looks worse and works worse. With Safari this is not the case. There is no "Oh this website works better with Firefox, you should install it" which is likely the biggest factor for browser adoption and my gut feeling says that Apple knows and uses this. This particular statement seems questionable: > My main point is that Safari is not flouting or disregarding established W3C/WHATWG web standards but, rather, being very careful about how it implements those standards which takes time. In some cases their actions simply don't make sense, except if you look at it from a perspective of protecting their iOS App platform. For example breaking localStorage in the name of privacy (which is ridiculously paradox) and not supporting obvious, simple UX improvements like scroll-anchoring. Safari is in some cases stricter/more standards compliant than Firefox and especially Chrome. But in some cases like above the feature intersection of Firefox and Chrome is the one that makes the most sense for the web.