Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Was working fine, now broken in IE, code the same?!

Status
Not open for further replies.

DaRNCaT

Technical User
Dec 18, 2002
566
NZ
I've designed a site with CSS layout, given it to the developer, and it was until recently, working just fine, now the left side is all messed up in IE, now I know it's something to do with IE's box model whatsit, but I can't find any changes anywhere that would account for it, it simply doesn't work, but exactly the same site works fine in it's original state.

Thinking it was the added content, I stripped that all out, still won't work, what gives?!

How can exactly the same code, calling the same .css file, work fine on one .html page, but not on another?

Any answers most appreciated.

----------------------------------------
Sometimes, when my code just won't behave, I take it outside and make it listen to britney spears music, and when it comes back it's really well behaved. I wonder if it's suffering from post tramatic stress syndrome now..
 
Did you see this start to happen after you hosted it on a different server?

If so... it could be that the server is stripping out some of the whitespace (maybe \n or \r replacement) as it serves the page. I have seen this on a site that was served by a Tomcat/Apache server whilst it was perfect on an IIS server - does view source push all markup onto one line? - this is how I identified my problem.

Just a thought,
Jeff

[tt]Jeff's Page [/tt][tt]@[/tt][tt] Code Couch
[/tt]
 
Also inspect anything around the doctype. Your problem sounds like rendering in standards mode (your original code) and quirks mode (developer's) code. Even a comment before the doctype will throw off IE.
 
Make sure that the case of the CSS (and other) filenames is the same as the case of the reference to that file n the HTML code. It could be that the current host uses case-sensitive filenames, and your code has a mismatch (that wouldn't have shown up locally).

Incidentally, you have a spelling mistake in your signature - "tramatic" should be "traumatic".

Hope this helps,
Dan

[tt]Dan's Page [blue]@[/blue] Code Couch
[/tt]
 
Cheers,
I found the error, when the layout was split into include files, comments were added to the main page to seperate the includes, and one was added above the header include, which I think put it back into quirks mode.

Moral of the story, don't add crap above the doctype, even if it's within a full PHP page and doesn't look like it 'should' cause problems, sure had me scratching my head!

Hmmmm.... spelling, not my strong point, thanks for that, who knew traumatic could be so tramatically spulled ;)

----------------------------------------
Sometimes, when my code just won't behave, I take it outside and make it listen to britney spears music, and when it comes back it's really well behaved. I wonder if it's suffering from post tramatic stress syndrome now..
 
Well, I will going to congratulate myself for the reason that DaRNCaT managed to found the problem, although all I did was correctly point out the exact error without seeing anything. PSI rating 9+, baby.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top