It was only a matter of time...

this matches my own testing of the situation and fails to point out that IE7 compat-mode != IE7. (Microsoft is aware of this and seemingly working on patching the problems where they can... but now we effectively have two versions of IE7 to test for.)

"The links below include tests for three W3C specifications in various stages of development. These include CSS 2.1, HTML5, and ARIA."

"IE8 checks for the presence of IEStandards.xml file (on the root domain) only if it hasn’t been requested in the last 30 days for that domain."

Some notes on the differences between hAtom and Microsoft's hSlice.

Hrm, seems that sites in the compat mode list can be found in: "res://iecompat.dll/iecompatdata.xml

Philip Taylor finds a bug in IE8 (beta 2)'s localStorage implementation that causes data loss.

Daniel Glazman's company ported IE8's "web slices" feature to Firefox... it wasn't immediately clear to me from the description if this meant that an existing "web slice" would just work with WebChunks or not...

"XXX7 and XXX8: in IE these are called item and namedItem, but they have deep magic involved to resolve name clashes with form controls of those names. In other browsers, they are anonymous."

"The interface objects (constructors) and interface prototype objects defined for Beta2 are based on the structure and function of IE's internal object model. Early on, we had to decide if we wanted to implement a "fake" layer for the constructor/prototype objects that looked identical to the W3C model, or to expose what we had, warts and all. While the warts weren't particularly attractive, they do help to bring clarity to the way that the DOM is represented internally and avoid having a whole series of internal mapping bugs between what is actual and what is veneer."