intertwingly

Start with this page.  View with IE8.0.7000.0 from the Windows7 beta, first without javascript.  Then apply Sjoerd Visscher’s tip:

// allow IE to recognize HTMl5 elements
if (!document.createElementNS) {
  document.createElement('article');
  document.createElement('aside');
  document.createElement('footer');
  document.createElement('header');
  document.createElement('nav');
  document.createElement('time');
}

Result.  Renders considerably better than any previous beta or released version of IE.  The nav bar and data dropdowns aren’t repositioned because IE8 doesn’t implement document.addEventListener("DOMContentLoaded", ...), which I can work-around if I chose to.  Scrolling further down the page reveals a different problem...

Looking at the DOM, you can see the issue: after the first two articles, subsequent articles are nested.  Note that the svg element appears to be processed into a single node without the need for Sjoerd’s workaround.  I’m presuming that that is a result of IE8’s so-called Improved Namespace Support.

But I said “appears” above.  If I expand the svg node, I can see the individual path elements.  But if I go back to my source and remove those path lines from the HTML, the enclosing article will close correctly; the error simply moves down to the next article.

I’m presuming that this is a bug.