"Internet Explorer 8 is going to be the most standards-compliant IE yet, but it's going about it in a way that has some people scratching their heads. With Internet Explorer 8, you have a choice in standards compliance modes. Sound oxymoronic? Shouldn't there be one standards mode by default? Heck, shouldn't the only mode be standards mode? Ah, idealism." Please note, however, that John Resig of Mozilla Corporation
spotted something interesting:
"Internet Explorer 8 will support DOCTYPE switching for new DOCTYPEs (like HTML5). This really does change any frustration that someone should have concerning the new meta tag. This means that you can write your web pages in a completely standards-based way (CSS, HTML5, JavaScript) and not have to use a single browser-centric tag in order to do so."
Member since:
2006-11-22
Problem: How to deal with the pages coded to the old hacked rendering engine (instead of being standards compliant)?
MS Solution: Create a new hack.
Justification: We can't break the web
Reality: The only pages affected are the coded only to a non-standard rendering engine, not the bulk of the web anymore.
Alternative Solution: Make IE8 rendering standards compliant. The sites coded to IE specific rendering will have their code fixed to standards compliant rendering or be less useful.
Comments: Each new hack is a delay to actually fix the problem. This particular hack will probably only last a couple more versions of IE. The limiting factor will be the extra code for multiple rendering engines/rules in a browser. This hack also does not address the other major problem IE specific rendered sites face: greater adoption of standards compliant browsers. In the end most of these sites will have to be recoded to standards compliant rendering anyway. Anyone else notice that even the MS sites have been rewritten to render better in more standards compliant browsers like FF?