Linked by Thom Holwerda on Tue 4th Mar 2008 10:07 UTC, submitted by gonzo
Internet Explorer "We've decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we've posted previously. Microsoft recently published a set of Interoperability Principles. Thinking about IE8's behavior with these principles in mind, interpreting web content in the most standards compliant way possible is a better thing to do. We think that acting in accordance with principles is important, and IE8's default is a demonstration of the interoperability principles in action. While we do not believe any current legal requirements would dictate which rendering mode a browser must use, this step clearly removes this question as a potential legal and regulatory issue. As stated above, we think it's the better choice." Ars has more.
Thread beginning with comment 303307
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I am smiling right now
by lemur2 on Tue 4th Mar 2008 13:20 UTC in reply to "I am smiling right now"
lemur2
Member since:
2007-02-17

This is great.

I look forward to the day when I only have to write one page not have thousand tweaks to make it works with various IE-versions.


I think it is great too ... but note the caveat ... "interpret web content in the most standards compliant way it can"

It will still be quite a while before IE is actually standards compliant to any useful extent for your purpose. IE doesn't support SVG yet, and quite a few other web standards that a browser should support.

Reply Parent Bookmark Score: 2

google_ninja Member since:
2006-02-05

But it will fully support CSS now, better then FF2 does, which is the point he was trying to make. SVG support is kind of pointless at this point, as good webformats are the ones that focus on the smallest size possible, not the largest and most cpu intensive. SVG will be sort of like a poor mans flash when browsers start letting you script it, but until then I can't think of a single scenario where it would be a good choice for use on a web page.

As for other standards, which ones are you talking about? I would like everyone to standardize on XHR, but since MS was the ones that invented XMLHttpRequest in the first place, they could justifyably tell everyone else to take a flying leap on that one.

Reply Parent Bookmark Score: 3

RE[3]: I am smiling right now
by dagw on Tue 4th Mar 2008 16:41 in reply to "RE[2]: I am smiling right now"
dagw Member since:
2005-07-06

But it will fully support CSS now, better then FF2 does


All that means is that instead of having to tweak you CSS to work around features not implemented in IE, you'll have to tweak your CSS to work around features not implemented in FF2. Until all browsers use the same rendering engine (which will probably never happen), web developers will always have to make a choice between.

1) Writing to the lowest common demoninator subset of the w3c spec implemented by all used browser, which will probably be a small subset for the forseeable future.
2) Tweaking pages for specific browsers
3) Accepting that some pages will render incorrectly in some browsers.

Don't get me wrong I think it's great that MS is taking w3c compliance more seriously and I applaud them. However anybody who thinks that soon all they'll have to care about is if their page is w3c compliant and then it will magically work in all browsers is probably quite mistaken.

All IE8 and FF3 will change is making the subset in point 1 a bit larger once IE6-7 and FF1-2 become so old no one uses them any more. Web developers will always have to target browsers rather than specs.

Reply Parent Bookmark Score: 2

RE[3]: I am smiling right now
by SJ87 on Tue 4th Mar 2008 19:19 in reply to "RE[2]: I am smiling right now"
SJ87 Member since:
2007-12-16

But it will fully support CSS now, better then FF2 does, which is the point he was trying to make. SVG support is kind of pointless at this point, as good webformats are the ones that focus on the smallest size possible, not the largest and most cpu intensive. SVG will be sort of like a poor mans flash when browsers start letting you script it, but until then I can't think of a single scenario where it would be a good choice for use on a web page.


Afaik Opera and Firefox 3.0 already support scripting of SVG (to some extent). Maybe even Safari, too. And with Adobe having no slightest intention to support BSD or x64 systems, SVG could prove pretty useful quite quickly once it itself has gained support from web browsers.

Reply Parent Bookmark Score: 1