To read all comments associated with this story, please click here.
Only in a parallel universe. Microsoft themself spoke out loud just recently that please, please web-designers, not forget the IE.
Firefox and WebKit. That's the landscape. Both working together well on all platforms (including Windows) and usually if it works in one it does in the other too.
Its IE being far behind like still not supporting for example WebGL, still not working on THE major platforms Android and iOS.
Edited 2013-02-13 21:39 UTC
Three engines? Trident isn't worth testing, nobody uses IE except to download chrome or Firefox, unless they are forced to use it at work.
...I would love to be able to say.
I wish MS would make it multiplatform already, so I didn't need to virtualise just for their engine.
Edited 2013-02-13 21:26 UTC
I am currently testing a UK Very large client's customer-facing website.
Their usage stats looks something like below;
IE8 ~15% of all traffic to the site
IE9 ~20%
Firefox ~20%
Chrome ~30%
The rest is made up of other browsers or variations inc Opera and IE10. We simply can't justify the resource as a business to test theses browsers at this time.
I WISH I could stop testing IE8 (as does tend to throw up a number of issues on more advanced features) but the commercial reality is you cant ignore them.
I hope you actually look at the business requirements of your customers before deciding the the irrelevancy of a rendering engine





Member since:
2010-01-21
I have mixed feelings about this.
On the one hand, I'm concerned about whether three engines is enough variety to ensure that APIs and standards don't codify implementation details too readily when one of them has Trident's reputation for being something we only support because we're forced to.
On the other hand, I'm eager to have one less closed-source program sitting on my system just because I need to do compatibility testing.