Internet Explorer

Do It Right The First Time; Do Not Use Microsoft-Contrived Version Targeting

Microsoft announced in January that Internet Explorer 8 (IE8) would be standards-compliant, but only if you included a special meta tag or http header indicating that the page should be rendered in standards compliance mode. The uproar from the standards community led Microsoft to change the default behavior of IE8. Now IE8 will render all pages in standards mode by default, unless you specify otherwise with the X-UA-Compatible meta tag or http header. Interestingly, the Microsoft followers did not seem to feel short-changed as the standards advocates had.

IE6 DeathMarch

IE6 Death March has led the way in the movement to stop support for IE6. Help your web developers help you to save money, conserve their sanity, build better websites and make the internet a better place. With so many other great browsers available, IE6 is just not worth the effort anymore. If you think you really need to support IE6, I have two things to say to you;

Version-targetting in IE8

Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 is an A List Apart article that was Slashdotted. It explains a new convention/standard designed by the Web Standards Project and Microsoft that aims to improve the support for old websites when new versions of websites come out. It introduces a new meta tag and http header that specifies what versions of each browser the page is compatible with. Such a convention would, in theory, ease the pain when IE8 is released and avoid the frantic chaos that occurred when IE7 was released.
Syndicate content