IE8 goes Standard
It’s just true, developers look in utter disbelief when their IE6-perfect sites turns monsterous in IE7. This explains why in many parts of the world, people are still stuck with IE6. Because some louzy sites only work in IE6.
Microsoft the benign giant has been struggling hard to keep supporting sites on both IE6 and IE7, and now they’ll have even more dead brain cells with IE8. This time, Microsoft has done it right by coming out to make Standards Mode the default rendering mode in their upcoming IE8.
Microsoft says in their blog…
One issue we heard repeatedly during the IE7 beta concerned sites that looked fine in IE6 but looked bad in IE7. The reason was that the sites had worked around IE6 issues with content that – when viewed with IE7’s improved Standards mode – looked bad.
Now that IE8 has decided to go “Standard”, Microsoft is prompted with a second dillemma. Whether to choose to render default in IE8 Standards or IE7 Standards. Naturally, IE8 has better standards support than IE7 and it would be in the community’s best interest for IE8 to go IE8 Standards.
In other words, the technical challenge here is how can IE determine whether a site’s content expects IE8’s Standards mode or IE7’s Standards mode? Given how many sites offer IE very different content today, which should IE8 default to?
So, the conclusion is that IE8 will, by default, be IE8 Standards, not IE7 Standards, nor Quirks mode. This means thats
1. Developers that has always designed with standards will have no(or little) issue with the transition
2. Developers that don’t are screwed.
In a very practical manner, site owners that want to move their site to become standards-complaint, but wants a their legacy code to look correctly in other IEs might consider the header/meta approach (discussed here), but I am not sure if this is actually a IE-centric browser-sniffing work.
No Comments Yet