Hopefully the title says it all.
Why is this a programming question? If IE9 were to take a different approach to "compatibility" it would be relevant especially to maintaining legacy sites.
Hopefully the title says it all.
Why is this a programming question? If IE9 were to take a different approach to "compatibility" it would be relevant especially to maintaining legacy sites.
Microsoft is about 3 weeks into the project. I guess it is too early to tell. If you want to vote on features, visit http://connect.microsoft.com/IE.
I asked a similar question in SuperUser.com and it was closed as subjective and argumentative, except mine specifically asked whether it was being based on WebKit.
Given the fact that they have already greatly surpassed their previous values for compliance, I think they might have their sights set on that first.
I'm worried because I maintain a legacy app that will die without quirks mode myself.
The Platform Preview released now doesn't have a ‘compatibility view’ button yet — or any other buttons to speak of, as it's almost completely missing its UI — but it's clear that ‘compatibility view’ is here to stay:
The Platform Preview Build will use the IE8 Compatibility View Settings including the Compatibility View List. This means that if you’ve chosen to use the Compatibility View List in IE8, some high traffic websites will run in the IE7 Document Mode by default.
Quirks Mode has now been named ‘IE5 Document Mode’ in the interface, so you get to choose a browser quirkset from the menu for anything between IE5 and IE9 except IE6. Looks like Microsoft are stuck reproducing the bugs of every former version of IE into every future version from now on... that's the foot-shooting joy of OS integration I suppose.