Netscape causes table cells to disappear

liunx

Guest
This site works ok for IE, but when using Netscape 6, it causes table cells to disappear - the appearance of the pages seems to vary also(which I didn't think ever happened). <br />
<br />
Here's the site: <!-- m --><a class="postlink" href="http://68.209.232.250/coalition/">http://68.209.232.250/coalition/</a><!-- m --><br />
<br />
I attached a screenshot of what I got on one reload - it apparently varies in how it looks which I find odd. <br />
<br />
This is very strange to me: When I view the pages from outide of my IIS server, the table cells don't disappear. When I view then from my server (on my computer) the table cells seem to disappear and the pages seem to be different in how they look. <br />
<br />
Does anyone else get strange behavior with Netscape 6 on these pages?<br />
<br />
Thanks<br />
<br />
voltson<!--content-->look fine for me in 1e 5.5, netscape 7, mozilla<br />
<br />
or atleast they all look the same, they didn't appear like in your screenshot<!--content-->the only way cells can disappear in NS is if the code is invalid. NS is very picky when it comes to code, it is not like IE which lets you do anything even if it is bad code.<br />
<br />
you cannot have empty cells, at least put &nbsp; in them<br />
<br />
also you code has to be complete, you are missing a closing </td> after you first nested table. make sure all tags are nested properly and all the tags are actually there.<!--content-->Thanks for the info on Netscape. I just noticed the requirement of &nbsp ; yesterday. I just viewed the site with Netscape 4.7 and it looks fine. It seems like it would be fine in Netscape 6 then. Maybe I'll try it on another system. <br />
<br />
thanks <br />
<br />
voltson<!--content-->Heading towards perfect code: <!-- m --><a class="postlink" href="http://validator.w3.org/check?uri=http%3A%2F%2F68.209.232.250%2Fcoalition%2F&charset=%28detect+automatically%29&doctype=HTML+4.01+Transitional&ss=1&outline=1&sp=1&verbose=1">http://validator.w3.org/check?uri=http% ... &verbose=1</a><!-- m --> <br />
<br />
Just a few minor issues (unrelated to your bug) to tidy up.<!--content-->
 
Back
Top