Theme Jacked up in IE 6 and & - Fine in Firefox, Safari and Chrome
demian dellinger - November 17, 2008 - 23:47
The site I'm working on http://shoemadam.com is flawless in Firefox, Safari and Chrome but in IE 6 and 7 (and 8 beta) it is a disaster.
The theme is a theme I have used before with no problem from RoopleThemes.
What do I need to do to fix this?

hmmm
Wow. Big difference. Silly question: does the site work in Garland or another default theme? It might be a line of CSS (sometimes IE dislikes padding, margins, and other nice css features) or something else that's different from the time that you used it last that is causing the error.
I never had the site in a
I never had the site in a default theme, but that said I don't know that it ever looked right in IE, I don't really use it and usually just do a check in IE later.
I used the same theme on a different site http://beachsalerealestate.com and it worked fine. There is an additional "outside sidebar" active on this version but even when that sidebar is not active (no active blocks) it is still jacked up in IE.
Well, start with the
Well, start with the obvious:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fshoemadam.com%2F
Your HTML is not just invalid in some areas, it's actually structurally broken with unclosed tags and things.
As a result IE thinks that all your content is actually inside sidebar-left. And tries to squash it to fit.
It's a syntax thing. IE is probably actually being strictly correct, and FF shouldn't have forgiven you those errors.
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
Learn something new everyday.
I'm quite sure this is useful. I'll have to muck around in the code to tweak this best I can.
Thanks for the obvious :)
Thanks A Lot
I was able to fix it enough to work. I was using the same faulty code for my images, over and over.
Thanks so much for your help! Go Drupal.
~W00T~
Great when there's a quick, logical fix!
It's actually a good thing that browsers are becoming more picky ;-)