The IE Blog has an important new post tonight discussion the “compatibility-view” improvements coming with IE8.
The next public update of IE8 (for Windows Vista- and Windows XP-based operating systems as well as the Windows 7 Beta) includes improvements to Compatibility View that help end-users when they visit web sites that are not yet ready for IE8’s new, more standards-compliant defaults.
Here’s the short background:
In IE8 Beta 1 the newest standards-based rendering was the default view. It was left up to site authors to trigger into the compat mode as needed. While reserving judgement on whether that was the right strategy, it’s fairly obvious that sites that aren’t up to standards are often sites without attentive staff on hand to throw the trigger. So users suffered.
In IE8 Beta 2, they added a “compat view” button to the browser’s button bar. Now, “savvy end-users” could drop into compat mode as needed. Unfortunately, again, it’s the non-savvy users most at risk of suffering a poor user experience. They don’t know to click the button.
Even though many sites have taken the last several months to update their code bases to be ready for IE8, MS’s data shows that many major sites are still at risk. Furthermore, “We could also see from our instrumentation that not all IE8 visitors to those sites were clicking the Compatibility View button. So, large groups of people were having a less than great experience because they weren’t aware of the manual steps required to make certain sites work.”
Which brings us to tonight’s post. When users install IE they will be able to opt-in to what I’m calling “crowd-sourced compat mode toggling”
The system has some nice design elements. In addition to monitoring overall popular sites for user behavior they’re also maintain regional (and presumably segmentation) lists of top sites so that the Top N sites (they can’t track all sites) globally don’t drowned out popular regional sites.
Another positive: They indicate that sites will be able to opt-out of this program if they wish.
On the negative side, it seems that “site” is only at the top-level-domain granularity. I suspect they’ll want to revisit this because some large networks have very diverse subdomain properties. One size doesn’t fit all in this case. (Perhaps they could look at the scope of the cookies set by the domain?)
Another potential negative is that it seems like they’ll only be pushing the list out every two months. That’s awfully slow it seems.
All in all, not a bad idea. We’ll see how the implementation details play out.