Internet Explorer Madness
Comments: 7
I rarely use IE these days and now that I’ve dusted it off to test the new design it seems to be punishing me for abandoning it. Why would it completely choke on a page – as in refuse to display anything at all – simply because of the standard XML declaration at the beginning of a file:
If I remove that line, everything’s fine in IE 5.2.2 under OS X. Is this some weird bug I don’t know about? I googled around but couldn’t find a reference. The weirdness continues because I can visit a site using the same declaration and document type and IE renders it fine.
•••
Posted to Computers • 2002.10.11 (Fri) • 23:58
Comments
Posted by Ed 2002.10.12, 04:25
I had a similar problem once (but on IE6/Win), and I easily solved it by ensuring no headers (as in the PHP header() function) were sent to the browser before the !DOCTYPE declaration.
Posted by Mike Steinbaugh 2002.10.12, 06:01
Yeah make sure the DOCTYPE comes first. That’s right on. Also, I’m getting a weird ActiveX notice that pops up every time I visit the page in IE 6 because Antipixel is trying to play a sound file. You might want to look into that. The right hand column doesn’t appear in IE anymore too. It works fine in Mozilla for me though. Don’t you just love the DOM quirks in browsers? I know I do…so much fun.
Posted by Ryan Carter 2002.10.12, 08:08
Yeah, like Mike said, in IE6, the right hand column is no longer there at all. (Previously it was just pushed WAY down the page.. then it was fixed… but now it’s just plain gone.) No problems in Mozilla though.
Yes, DOCTYPE’s can really be quirky… I’m currently touching up a site I built about 2 years ago (it uses frames :eek: ) and trying to get the frameset doctype to do what I want it to just isn’t happening… (I really hate having to use frames, or tables, but the client just won’t budge on certain things…) ho-hum…
Posted by jh 2002.10.12, 12:10
That’d be right — everybody knows the start with the !doctype except me! Still can’t figure out why it would be fine on some pages, though. DOM quirks indeed [yanks out last remaining strands of hair].
As for the disappearing column, jeez, I give up. Nothing’s changed, code-wise, the page is validating just fine, and there doesn’t seem to be a long string or wide image in the column that would force the break (which should just run it to the bottom below the remaining two anyway). I just want a set of fucking standards I can adhere to religiously and know they’ll work. But then, don’t we all.
The new design should be a little more robust as far as the columns go and I can only hope it doesn’t introduce too many other things that like to break. Going to try to finish the templates up over the weekend and will shoot for getting MT 2.5 on the existing site as well.
Posted by Ryan Carter 2002.10.12, 20:02
Hehe… column’s back ;)
Posted by resonance 2002.10.12, 23:18
Every once in a while, and this was a long time ago for me now as well, since IE has been demoted to my “testing” browser, IE on OS X chokes on something as simple as an image aligned right or left. I’d have to put the image in a table of the same dimensions as the image, then align the table left or right to prevent IE from freezing when loading the page.
Of course, you fancy-schmancy CSS folk wouldn’t know anything about this, would ya? Nah, you just let your stylesheets do all the work for you…grumble…grumble… ;)
Posted by Muraii 2002.10.13, 07:32
I assume that the colon at the end of your first paragraph of the post indicates that the space between paragraphs is to be inhabited by some text, ostensibly the offending line of code.
I’m on IE 5.50.4134 and the line won’t display at all. That’s fine if my assumption is incorrect, which is the odds-on favorite, but I thought it wouldn’t hurt to transform some electrons into ASCII and let you know.
Post a comment:
Send This Story to an Enemy
• • •
