Main Area and Open Discussion > General Software Discussion
Current IE8 build renders the ACID2 Test correctly!
nontroppo:
you're welcome ;)
Lashiec:
Breaking news! In a effort to improve standards compliance in IE8, Microsoft reinvents the Web. The Internet breaks loose
In related news, the HTML5 draft is published. List of changes
(6 links in two lines. Gotta catch them all!)
nontroppo:
Ian Hickson's take:
If Web authors actually use this feature, and if IE doesn't keep losing market share, then eventually this will cause serious problems for IE's competitors — instead of just having to contend with reverse-engineering IE's quirks mode and making the specs compatible with IE's standards mode, the other browser vendors are going to have to reverse engineer every major IE browser version, and end up implementing these same bug modes themselves. It might actually be quite an effective way of dramatically increasing the costs of entering or competing in the browser market. (This is what we call "anti-competitive", or "evil".)
--- End quote ---
Big sites will become locked in to particular IE version numbers, unable to upgrade their content for fear of it breaking. Imagine in 18 years — only twice the current lifetime of the Web! — designers will not have to learn just HTML, they'll have to learn 4, 5, maybe 10 different versions of HTML, DOM, CSS, and JS, just to be able to maintain the various different pages that people have written, as they move from job to job.
--- End quote ---
http://ln.hixie.ch/?start=1201080691&count=1
From Opera's Hallvord Steen:
Browsers will have to support an unmanageable and confusing mess of different rendering modes (and the PocketIE team will hate you for the bloat).
Because the META tag affects every part of the page, progressively enhancing such pages with new CSS features will be harder.
--- End quote ---
http://my.opera.com/hallvors/blog/show.dml/1688321
And more from Mozilla's Robert O'Callahan:
<META HTTP-EQUIV="X-BALL-CHAIN">
--- End quote ---
;-) http://weblogs.mozillazine.org/roc/archives/2008/01/post_2.html
The webkit team also ain't drinking the coolaid:
So, in conclusion, we don’t see a great need to implement version targeting in Safari. We think maintaining multiple versions of the engine would have many downsides for us and little upside.
--- End quote ---
http://webkit.org/blog/155/versioning-compatibility-and-standards/
This is like an 8.5-9 on the web developer richter scale...
nontroppo:
And specifically related to Acid2 and IE8, Ian Hickson (who authored Acid2) says this:
It will be interesting to see whether IE8 really supports Acid2, since that test page doesn't include any of the special magic words being proposed here. Will they hard-code the URI? Will they check every page against a fingerprint and if it matches the fingerprint of the Acid2 page, trigger the IE8 quirks mode instead of the IE7 quirks mode?
--- End quote ---
Note Acid3 is also in the works and getting close to completion:
http://ln.hixie.ch/?start=1200301306&count=1
justice:
It's hard to see how it works out and whether or not this is a good solution or not to me personally. But ever since the development restarted on Internet Explorer the team and Microsoft in general have been supporting standards (at least minimally), so to me version targeting shows that they still don't think the web can be standard based. Or big corporate partners can't afford the cost of converting to standard. Still though I've not made up my mind on it from a practical perspective.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version