DavidOverton.com
This site is my way to share my views and general business and IT information with you about Microsoft, IT solutions for ISVs, technologists and businesses, large and small.  
David Overton's Blog » All Tags » Open Standards » Internet Explorer (RSS)

Browse by Tags

  • Internet Explorer goes for standards 1st - Microsoft's Interoperability Principles and IE8

    IE8 is cooking along nicely. IE is one of those products that is highly impacted by standards and given the announcements Microsoft made about standards and interoperability last week, the IE team have made some announcements ( IEBlog : Microsoft's Interoperability Principles and IE8 ) Microsoft's Interoperability Principles and IE8 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. 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...

  • Web Developers were just tooo smart for their own good - they got web pages to look just right in IE6 and didn't see Microsoft fixing the compatibility issues (or some of them) for IE7. Now IE8 has to clean up it's and others mess

    OK, so the title is mine, but you can see here how the defacto standard that was IE4/5/6 meant that people thought IE7 would live by the same rules. If you care about "standards based websites" then the IE team blog on compatibility is a must for you. Compatibility and IE8 In Dean’s recent Internet Explorer 8 and Acid2: A Milestone post, he highlighted our responsibility to deliver both interoperability (web pages working well across different browsers) and backwards compatibility (web pages working well across different versions of IE). We need to do both, so that IE8 continues to work with the billions of pages on the web today that already work in IE6 and IE7 but also makes the development of the next billion pages (in an interoperable way) much easier. Continuing Dean’s theme, I’d like to talk about some steps we are taking in IE8 to achieve these goals. I’ve been on the IE team for over a decade, and I’ve seen us apply the “Don’t Break the Web” rule in six different major versions of IE in different...

  • Internet Explorer 8 (yep, not yet released) does standards (well Acid anyway)

    Earlier this month on the IE blog there was some discussion about IE8, almost the 1st discussion about this - Internet Explorer 8 . Now they talk about the "Standards Mode" and how for those who want near 100% standards based web sites can live happily together. It is worth saying that it might end up 100% standards based, but since I don't think such a thing exists, all I will say is that is passes all the standards tests. Acid is one of these tests. I strongly recommend you read the the whole blog Internet Explorer 8 and Acid2: A Milestone As a team, we’ve spent the last year heads down working hard on IE8. Last week, we achieved an important milestone that should interest web developers. IE8 now renders the “ Acid2 Face ” correctly in IE8 standards mode. If you’re not a web developer, the details of this blog post probably aren’t all that interesting for you. I’d like you to know that we’re building IE8 for many different customers (consumers, web service providers, independent software vendors...

(c)David Overton 2006-23