Joshua wrote:
Marcello Perathoner wrote:
<HEAD> <STYLE type="text/css" title="red"> P { color: red } </STYLE> <STYLE type="text/css" title="blue"> P { color: blue } </STYLE> <STYLE type="text/css" title="green"> P { color: green } </STYLE> </HEAD> <BODY> <P>Don't show this to any DP Project Manager. </BODY>
It is also extremely annoying that IE triggers quirks mode if you include an XML prolog at the beginning. <?xml version="1.0" encoding="utf-8"?>
Thanks for the link to quirksmode.org. I was aware of the quirks/ strict mode switches of browsers (based mostly on DOCTYPE), but didn't realize that IE6 messed things up vis-a-vis the XML prolog: "In Explorer 6 Windows, Microsoft implemented one extra rule: if a doctype that triggers strict mode is preceded by an xml prolog, the page shows in quirks mode. This was done to allow web developers to achieve valid pages (which require a doctype) but nonetheless stay in quirks mode." This is very lame. Microsoft simply assumed that no one will ever include the XML prolog in a finished online HTML page, so they invoked this rule for testing purposes! (There are certainly other ways they could have used to force quirks mode, like a "always quirks mode" menu selection.) Hopefully the announced IE upgrade (supposedly to me more CSS standards conformant -- a result of the pressure from Firefox and Opera) will fix this. But I'm not holding my breath. Jon Noring