Quote:
Originally Posted by student4ever
you know what the real solution is? We all need to organize and stop designing for IE, that way, people will stop using it and we can work with some standards!
|
It's actually the other way around. IE is properly interpreting the page as XHTML, which is what the DOCTYPE says to do.
Because the H1 tag wasn't closed, and DIVs are not allowed within H1 tags, it made the *correct* move by basically cascading the H1 styling into the rest of the content.
Firefox and the others broke the rules by assuming the H1 tag had to be closed at the first DIV that was encountered, and unilaterally made a fix. The browser internally closed the H1, and in doing so the page was properly displayed.
When the DOCTYPE is set to a loose HTML standard, IE will (usually) apply the internal fixes that you see Firefox did, and the page will display correctly. You'd expect that, as XHMTL is supposed to have been validated.
As a reminder, WordPress will correct the XHTML for posts (so that RSS feeds work), but it won't for any content outside of a post - which includes headers, footers, and sidebars. I always like to test a new theme, or retest one I've changed, to make sure I'm still compliant.