1 marston Feb 18, 2005 03:14
3 marston Feb 18, 2005 03:43
Jesus christ!! I just noticed that too! Man, I haveta fix my damn site in mozilla now! :roll: That's computers and humans for ya'.
It was an overflow:hidden tag that I accidentally left in. Looks fine now.
4 edb Feb 18, 2005 03:54
Yeah much. I did a quick scan of your main - hacking out chunks to see what I could see and I did end up with a /div inside your posts loop that I think doesn't belong there and probably should be after you close your table out. Not sure though.
Oh hey the skin looks sharp by the way.
5 yabba Feb 18, 2005 14:57
I think you meant to have a wrapper div after this, that you forgot :-
<td width="60%" align="center" valign="top">
<!-- MAIN AREA BEGINS... -->
You're closing the missing div just before the </td> which is what's throwing the errors.
?
6 marston Feb 18, 2005 15:56
Er, I'm actually closing a <div align> tag... but I'll try putting another wrapper in and removing the unique div... Nothing else has worked so far! :-/
7 marston Feb 18, 2005 16:23
!!YEAHHHHHHHHHHHHHHHHHHHHHH!!!
VALID XHTML AND CSS!!!
Thanks so much for the help, EdB, and ?????!!!
By the way, thanks for the compliment, EdB :D !!
8 yabba Feb 18, 2005 17:00
No problem, glad you got it validated ;)
?
Um... wow. Your page looks okay in IE, but in Mozilla it just falls apart all over. One thing I see without looking too deep is that you start body, center, div id wrapper, table, but way at the end you close a table then center then body. Might be more than one table, but seeing how your page does one of those 'impressionist artist on acid' jobs in Mo makes me think it's a big part of your issue.
Also I don't know how tables react to having "div id blah" opened up inside them. Might be no problem, but it stuck out as something I'd wonder about. Classes work okay - I just don't know what the W3C says about what you can and can't put inside a table.
Mostly I'd be going after making sure each div is opening and closing at the right time. Save your main as-is and another copy to start hacking "div blahblah" to "/div" out of until you find a stray div either not closed or closed when it shouldn't have been. Easiest place to start that path is the sidebar, but anyway that's where I'd be looking.