W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2003

Re: how to square netscape 4 compatibility with css

From: Jason Ramsay-Brown <jramsaybro@hotmail.com>
Date: Thu, 20 Mar 2003 05:09:57 -0500
To: julia@we3.co.uk, w3c-wai-ig@w3.org
Message-ID: <F267mlegh0YCaRW5ER800000c7b@hotmail.com>

Hi Julia,

Without knowing specific's it's hard to render advice.  That said, I have 
been in this situation myself and may be able to lend some assistance.

If you can send us all some links, that'd be helpful.  But here's a short 
list of some helpful hints.

1. If you want to obscure CSS classes from NS4, move the classes into a 
separate file and make use of media="all" which causes NS4 to reject the 
stylesheet (example <link href="/css/nsbug.css" type="text/css" 
rel="stylesheet" media="all">). One might argue this is inappropriate, but 
unless you have multiple versions of the site formatted for different 
devices the technique is generally considered acceptable.

2. View source once the page is rendered and run a find for "Ttyle".  If you 
find it, you will discover some wonderful ugliness that only this browser is 
capable of.  It has to do with document.write, and the only solution is to 
ditch style attributes in favour of classes.

3. If you are using <meta http-equiv="Content-type" 
content="text/html;charset=something-or-other"> in your header then drop the 
charset reference (eg: <meta http-equiv="Content-type" 
content="text/html">).  NS4 bugs out if the browser preference differs from 
the declared charset.

Normally the 3 points above are what break NS4, but let us know if there are 
more specific issues we can help you deal with.



----Original Message Follows----
From: Julia Collins <julia@we3.co.uk>
To: "'w3c-wai-ig@w3.org'" <w3c-wai-ig@w3.org>
Subject: how to square netscape 4 compatibility with css
Date: Thu, 20 Mar 2003 09:21:39 +0000
MIME-Version: 1.0
Received: from mail01h.rapidsite.net ([]) by 
mc6-f19.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 20 Mar 
2003 01:25:22 -0800
Received: from frink.w3.org ( mail01h.rapidsite.net (RS ver 
1.0.78vs) with SMTP id 2-0635852112for <jramsaybro@websubway.com>; Thu, 20 
Mar 2003 04:21:53 -0500 (EST)
Received: from frink.w3.org (localhost [])by frink.w3.org 
(8.12.8/8.12.8) with ESMTP id h2K9Kb4g023637;Thu, 20 Mar 2003 04:20:37 -0500 
Received: (from lists@localhost)by frink.w3.org (8.12.8/8.12.8/Submit) id 
h2K9KaiB023613;Thu, 20 Mar 2003 04:20:36 -0500 (EST)
Received: from tux.w3.org (IDENT:root@tux [])by frink.w3.org 
(8.12.8/8.12.8) with ESMTP id h2K9KU4g023551for <w3c-wai-ig@frink.w3.org>; 
Thu, 20 Mar 2003 04:20:30 -0500 (EST)
Received: from tungsten.btinternet.com (tungsten.btinternet.com 
[])by tux.w3.org (8.12.8/8.12.8) with ESMTP id h2K9KTrB015308for 
<w3c-wai-ig@w3.org>; Thu, 20 Mar 2003 04:20:30 -0500
Received: from host217-35-7-177.in-addr.btopenworld.com ([] 
helo=[])by tungsten.btinternet.com with esmtp (Exim 3.22 #23)id 
18vwDs-0004qr-00for w3c-wai-ig@w3.org; Thu, 20 Mar 2003 09:20:28 +0000
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
Resent-Date: Thu, 20 Mar 2003 04:20:36 -0500 (EST)
Resent-Message-Id: <200303200920.h2K9KaiB023613@frink.w3.org>
User-Agent: Microsoft-Entourage/
Message-ID: <BA9F38A3.497%julia@we3.co.uk>
X-Archived-At: http://www.w3.org/mid/BA9F38A3.497%julia@we3.co.uk
Resent-From: w3c-wai-ig@w3.org
X-Mailing-List: <w3c-wai-ig@w3.org> archive/latest/16342
X-Loop: w3c-wai-ig@w3.org
Sender: w3c-wai-ig-request@w3.org
Resent-Sender: w3c-wai-ig-request@w3.org
Precedence: list
List-Id: <w3c-wai-ig.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Unsubscribe: <mailto:w3c-wai-ig-request@w3.org?subject=unsubscribe>
X-Loop-Detect: 1
Return-Path: w3c-wai-ig-request@w3.org
X-OriginalArrivalTime: 20 Mar 2003 09:25:22.0843 (UTC) 


Without wishing to seem immodest, I have written a fabulous javascript and
table free site where all layout and navigations are controlled by css. It
works beautifully in netscape 6+ and IE4+ on Mac and windows and fails
gracefully where stylesheets are not supported. (it is also fully accessible
for people using screenreaders).

My problem is, my client, who is large and archaic, has about 7,000 PCs
running netscape 4 only.  So it is important to write a site that looks good
for them.  Thing is, while it works, it looks s*** in that lovely browser.

I have been fiddling around and found a few workarounds which make the
situation a bit better, but it still looks like a bad web design in NS4,
with boxes all misaligned, rollovers not working (which I can live without)
and "strong" citations misaligning.

What do I do?  I am sorely tempted to write to the head of IT at the client
organisation and say that if they want W3c compliant, accessible sites
(which they demand, quite rightly) that look good at their end (which is
important to them) then they have to install standards compliant browsers on
their machines.

I have to stress that the site works in NS4, it just looks awful.

Any thoughts?




Help STOP SPAM with the new MSN 8 and get 2 months FREE*   
Received on Thursday, 20 March 2003 05:10:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:14 UTC