Finally I had some time to test Internet Explorer 8 beta 2, so first of all I ran all the test I had previously done to check if bugs were fixed.
Here’s the list:
:first-childselector to dynamically added element still doesn’t work, see the testcase. When you click on “Add first child” button, a new paragraph is added which then becomes the actual first-child of the parent div and only this new paragraph should apply CSS rules defined for the corresponding
:first-childselector. In IE8b2 new element gets the CSS applied, but the element that previously was first-child doesn’t lose CSS as if it still was the first child (see IE8b2 screenshot and Google Chrome screenshot).
:last-childis still not supported. Of course, it’s CSS3, but it would be really handy to have this supported and most browsers already support
:last-child. See testcase.
- Now about bugs that I blogged about here and here:
- position: relative for the generated content rule — fixed — now the testcase doesn’t kill the tab where it’s been opened.
- generated content is created after window.onload — fixed — now all the generated content is created right at the stage of applying CSS rules which can be clearly seen here.
null— fixed — now IE8b2 correctly shows the value of class attribute.
content: attr(className)results as an empty string, right as it’s defined in the CSS spec for non-existing attributes. Here’s the testcase.
- expressions don’t work in generated content — expressions don’t work in standards compliancy mode any more at all, so this bug is outdated
text-transformdoesn’t work for generated content — fixed — see testcase.
text-indentdoesn’t work for generated content — fixed — see testcase.