3 replies [Last post]
qwerty
Offline
newbie
Somerville, MA
Last seen: 15 years 38 weeks ago
Somerville, MA
Timezone: GMT-5
Joined: 2003-10-29
Posts: 5
Points: 0

Hi. This is my first time in the forum. I'm a search engine optimizer and not a designer, but I'm trying to fix a client's design before I fix its content and I'm running into CSS troubles.

They had been using numerous levels of nested tables, so I'm trying to replace most of that with layers. The page looks ok in IE6, but it breaks when I open it in Mozilla.

Any advice from folks who know this stuff would be greatly appreciated. The latest version of the page is here.

Tony
Tony's picture
Offline
Moderator
Brisbane
Last seen: 5 days 23 hours ago
Brisbane
Timezone: GMT+10
Joined: 2003-03-12
Posts: 5342
Points: 2963

Mozilla trouble

Hi qwerty,
The first thing I would do is check that you are using a doctype which puts the page into strict or standards mode.
This at first may mess up IE6 a bit but you will be able to fix it and as you do the other browsers should mostly follow.

There are some good links to articles on doctypes at http://www.csscreator.com/links/linkspage.php

Hope that helps.

qwerty
Offline
newbie
Somerville, MA
Last seen: 15 years 38 weeks ago
Somerville, MA
Timezone: GMT-5
Joined: 2003-10-29
Posts: 5
Points: 0

Mozilla trouble

Thanks for the suggestion.

I've added a 4.01 transitional doctype, and surprisingly, it still looks good in IE6. I tried validating it, and of course it failed, but a lot of that is because of all the Bravenet nonsense my client is calling from the page, and I can't change that. I did fix most of the other errors, however. There's still a row of <td> tags with a background image in there, and I know that isn't kosher, so I need to think about how to get that to work differently.

But there's been no change in the way it displays in Mozilla or NS7.

qwerty
Offline
newbie
Somerville, MA
Last seen: 15 years 38 weeks ago
Somerville, MA
Timezone: GMT-5
Joined: 2003-10-29
Posts: 5
Points: 0

Mozilla trouble

An update: now only the top layer is displaying incorrectly, and it's doing it in all browsers. I guess that's an improvement of sorts... :?