follow up

should have said this before, but vim also seemed to interpret it the same way as IE (the syntax highlighting I mean). also interesting to note is that vim didn't like "onload" attribute, but it checked out in the w3c validator.
also interesting: there is this one page I had that was giving out php warnings before any XML info or anything. it was a known issue that i knew i needed to fix.
anyway, IE refused to render that page, and guess why:

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.


--------------------------------------------------------------------------------

Only one top level element is allowed in an XML document. Error processing resource 'http://hosting.ctengel.net/kog/static.php?doc=Main'. Line 2, Position 2

Warning: file_get_contents(data/Main): failed to open stream: No such file or directory in /home/ctengel/public_html/hosting/kog/static.php on line 13

-^

no sh*t shurlock. yeah it is invalid. actually, i don't have too much of a problem with IE doing this. it is technically correct. but for the fags who say IE is better "cuz its more tolerant of my sh*tty coding"---YOU ARE WRONG. here there is a slight error. there is a bit of stuff before any formal opening. Firefox guesses (correctly) how I would like this to be rendered, and just slaps it above everything else.
Let me make myself clear: there is no right or wrong way to render this. some extremists (depending on my mood, i can be rather extreme, not that much though) might argue that IE did a better job here. I'm just saying this to prove all those ppl who say that IE guesses better wrong.

anyway, now for the real followup. this can be modified for screwball IE to get it right (while also preserving XHTML 1.0 Strict compliance) by making the original script tag be non-self-closing (removing the / that IE forgot) and slapping a close script tag immidiately after.
now to decide: shall i indulge in the geeky humor of dissing IE, or shall i play it safe by just making the site "work" in IE (the former does have the advantage of not requiring me to do a good job or finish it)