|
IE8 and Standards: Change for the *right* reasons by Acidus at 3:38 pm EST, Mar 4, 2008 |
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.
This is huge. And the correct decision. Bravo IE Team! Why Change? 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.
[sigh] This statement hurts you. You should do this because its the right thing to do for the Web, not to remove "a potential legal and regulatory issue." or to in accordance with Interoperability Principles (which hopefully weren't discovered solely while writing a 2.6 billion dollar check to the EU). I don't think the IE team wants to make a non-standards compliant browser. Or simply a Silverlight terminal. At least I hope not, and I'm willing to give you the benefit of the doubt (take note Sarah and Andrew). But don't tell us you are doing something because you have to, tell us you are doing something because it makes the web a better place. Doing the right thing consistently helps to reconcile 6 years of neglect far more than upbeat blog posts of questionable accuracy. I'm willing to give you a second look, but make it for the right reasons. |
|
RE: IE8 and Standards: Change for the *right* reasons by Stefanie at 10:29 am EST, Mar 5, 2008 |
Going Forward Long term, we believe this is the right thing for the web. Shorter term, leading up not just to IE8’s release but broader IE8 adoption, this choice creates a clear call to action to site developers to make sure their web content works well in IE. This topic is one of many things we’ll talk about with respect to IE8 at MIX this week. Thanks, Dean Hachamovitch General Manager Internet Explorer
Granted, it wasn't the primary reason, but at least he mentioned it in the last paragraph. Whatever the motivation, I think most will agree that it's a welcome change. Whether they'll lure current Firefox, Opera, and Netscape users to IE is another matter, though. |
|
|
|