Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Netscap6 and css

Status
Not open for further replies.
Jul 28, 2005
358
FR
Hi,

I have been developing a site for a client and have been testing it in IE, Firefox and Netscape.

My client has been complaining that Netscape (and safari on th e Mac) render horribly. Now I don't have access to a Mac, but as far as I was able to tell netscape was fine. Then this morning I find that they are using Netscape6 while I am using 8.0.4. I install Netscape6 and indeed it looks horrible.

I have resized text input boxes (and drop downs)and the text in the boxes is bottom aligning and cutting off the bottom of the text.

Also, I use css to resize images but NS6 doesn't do it. The code I am using to resize is:
Code:
.resizedImage img {

 width:139px;
 height:118px;
 border:1px solid black;
}

If anyone can shed some light on what may be happening and how to fix it I would be very grateful.

Richard
 
Netscape 6 should have a fairly decent css support although it was a seriously buggy version and should not be considered as a necessity to support. However, Safari has never caused any problems for me in regards to code. Can you show us the page in question or more css & html so we can debug this easier. As for Netscape 8, it has built in IE engine, so it can render things as bad as IE if desired.
 
Yep sure,

go to and look at the two blocks with forms in them. For some reason the top horizontal form displays correctly but the others are off.

By the way, I got the image resize issue fixed. it seems that NS6 is picky with case sensitivity for css where FF and IE are not.
Richard
 
Ok,

I am using
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
but it's not making blind bit of difference. (woul have used 4.01 but it screwed things up and I don't have time to change now).

Richard
 
Well, 3.2 would be stretching a bit into old and obscure doctypes. If your page design breaks with a complete 4.01 doctype, then your coding was bad, and there is a good chance you will get a satisfactory cross-browser result by using that doctype and fixing the problems. If you're unwilling to do that, all you're left with is simply addressing every problem with a N6 ready and mauling it as long as it takes to get a good solution.
 
It's OK now,

My client has finally agreed that NS6 is old and not worth bothering about. I do need to look at the 4.01 standards and sort some of the coding out (mainly css stuff that messes up).

Thanks anyway,

Richard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top