Forum Moderators: open
The pages and CSS I have created for the redesign did validate for XHTML 1.0 Strict and CSS2. They just haven't been made public yet until I finish the entire site and work out the bugs like this one. I only have three test pages uploaded to the server.
So far I've spent two weeks changing all the pages from layout tables to CSS absolute positioning and fixing my HTML soup that FP2000 generated so that it will validate.
I saw a similar problem once that manifested only on MAC Internet Explorer. A dozen other browsers on several platforms shows the content correctly while MAC IE showed the menu panel but not the content one.
In that site, the menu and content were separate divs, but still wrapped in a two-cell table (because that was miles better than trying to remove the table completely). But, somewhere during R&D, the content style gained a "float: right". That was enough for MAC IE to treat it as hidden.
Try using this one exactly as it's written, complete with the line breaks:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
So far I've spent two weeks changing all the pages from layout tables to CSS absolute positioning and fixing my HTML soup that FP2000 generated so that it will validate.
Hehehe, don't even go there! FP generated? That's not a valid excuse. I write valid html and xhtml in FrontPage every day. It is how you use the program, not the program itself. ;)
In regards to NN6.2, have you tested in other non IE browsers? Opera? Mozilla? Any Gecko based browsers besides NN?
I remember a distinct problem with FP and NN4.x where the closing </body> tag would end up missing. IE was forgiving and would display the page, NN4.x would not. I used to use NN4.x to validate code. If you could get it to work in NN4.x, it would work just about everywhere else.
When content does not display, the containing element is the first place to look. Any improper nesting, missing tags, etc. will all cause problems in certain browsers.
If the page does validate, and the display problem is still there, then it is probably a <div> related issue since you just switched from tables to css. Also, I hope you did not try and recreate tabular data with CSS. There is still a requirement for tables when tabular data is present.
I have no idea where the problem is being caused. I don't even know if it's in the external CSS or in the page code.I'm just going to drag the whole mess over to the little trash can on my desktop and start over.
That's a bad idea. Remove sections of it bit by bit until it works. Then you can isolate where the problem lies. Create differing versions of the page - ones with different doctypes, stylesheets, etc. Then you'll find the problem.