Forum Moderators: open

Message Too Old, No Replies

XHTML and CSS both validated at W3C

yet content does not display in Netscape 6.2

         

aroach

3:40 pm on Jun 9, 2003 (gmt 0)

10+ Year Member



I was under the impression that if your code validated that you were safe from lousy browsers. Apparently this is not so.

All NS6 gets is the left navigation panel. Nothing else displays.

Where do I go from here?

victor

3:58 pm on Jun 9, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Being valid sadly doesn't exclude all possible browser incompatibilities.

But the site in your profile does not validate cleanly. It has invalidly-nested table elements. I don't know if that is the cause of the problem, but it'd be a good place to start.

aroach

4:55 pm on Jun 9, 2003 (gmt 0)

10+ Year Member



The site in my profile is the one being redone but the pages on the server are not the new pages. They were created before I had ever heard of validation and I know they are a mess which is the reason for the redesign.

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.

aroach

5:03 pm on Jun 9, 2003 (gmt 0)

10+ Year Member



BTW, I think the Tag Soup on the current site that is public does display in NS6. Go figure.

victor

11:24 am on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Can you post a *short* example that shows the problem?

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.

Hester

1:00 pm on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Could this one be the NS6 Doctype bug? I had a site that worked in all browsers I tried, until someone with NS6.2 said it wouldn't load. The result was the Doctype.

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">

hartlandcat

2:56 pm on Jun 10, 2003 (gmt 0)

10+ Year Member



Hey, Netscape 6 never really worked anywhere. Thankfully, it's used by very few, as most Netscape users (myself included) have upgraded to version 7.

Hester

3:12 pm on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Ah, but this is the problem. A whole department has just 'upgraded' from Netscape 4 to 6.2! We're talking 400 people. So now I have to make sure my site works for them.

aroach

6:24 pm on Jun 10, 2003 (gmt 0)

10+ Year Member



Can you post a *short* example that shows the problem?

No. 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.

pageoneresults

6:53 pm on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



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.

aroach

8:38 pm on Jun 10, 2003 (gmt 0)

10+ Year Member



It worked in IE 6, Mozilla 1.3.1, and Opera 7.1. It was even okay in Lynx and NS 4.06, just unstyled.

The only problem I'm aware of occurred in NS 6.2. Which I have yet to see in my stats. I see NS 3, 4, and 7 but no 6. So maybe I shouldn't care.

DrDoc

8:39 pm on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Also, make sure any HTML style comments <!-- --> are removed from your CSS and JS code...

drbrain

8:56 pm on Jun 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You don't do anything fancy with the z-index do you? like set it to -1...

hartlandcat

8:57 pm on Jun 10, 2003 (gmt 0)

10+ Year Member



Hester -- why on earth have they upgraded to the 2 years old Netscape 6.2, when they could've upgraded the much newer and more secure Netscape 7.0?

Hester

8:29 am on Jun 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I wish I knew! IT departments always seem to be one or two versions behind. I think they are wary of new versions incase of hidden bugs. Yet they go for a browser built on an unfinished engine!

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.

hartlandcat

7:04 pm on Jun 11, 2003 (gmt 0)

10+ Year Member



Lol, I hate IT teachers. (no offence anyone)