Since when is only testing in Chrome an acceptable way to develop web applications?
I wish the author had shown us some other browser results. I'm curious if the iframe changes affected Safari, Firefox, or Edge. (Others have noted that app cache is deprecated).
Lots of folks here like to compare Chrome's dominance with that of IE6 back in the day.
Unlike Chrome, IE6 was never popular because of merit. Unlike Chrome, IE6 held back progress on the web - Chrome is still pushing it forward. Until that changes, can we quit with this tired comparison?
Is its a point of view only in people that are to young to have lived the debacle of IE6 years ? Or do some senor devs actually think testing in chrome only is ok ? Cause I read it more and more, and I find it very alarming. If this becomes a trend, we are going to live in pain all over again.
> If this becomes a trend, we are going to live in pain all over again.
It's painfully obvious that we're heading that way.
In a way Safari[0] and Apple's tight-fisted control on iOS is a blessing because no matter how much developers gripe about Mobile Safari (for plenty of good reasons mind) they damn well have to test the sucker.
[0] despite being "the new IE" to people who have no understanding of what it actually was and why it was a problem.
I wonder how much that is distorted by the aggressive preloading that chrome does and by android (since testing chrome on desktop and mobile is not really the same thing)?
I wish the author had shown us some other browser results. I'm curious if the iframe changes affected Safari, Firefox, or Edge. (Others have noted that app cache is deprecated).