Re: CSS stops working, and class problem.

Netscape originally tried to implement Javascript Stylesheets instead of
Cascading Styles Sheets. The difference being that each object attribute was
directly mapped to a DOM object property. So, instead of writing a style
sheet to, say, make the text blue or red, you'd set the text.color property
of the object to be "#ff0000" or "red" eg:

myobject.text.color = "#ff0000";

or

myobject.border.top = 2

etc

This approach was relegated to 2nd string status by the W3C when it ratified
CSS as the recommended approach.

Hope this helps.

BTW: The result is that in NN4.x CSS requires JS to work properly.

Steve Baty
Technical Designer
Red Square Productions
http://www.redsquare.com.au
steve(at)redsquare.com.au
Ph: +612 9519 4599
Fax: +612 9519 4699
-----Original Message-----
From: Rob Parker <RobParker(at)access.net.au>
To: Eric A. Meyer <eam3(at)po.cwru.edu>
Cc: hwg-style(at)hwg.org <hwg-style(at)hwg.org>
Date: Saturday, 30 October 1999 22:51
Subject: Re: CSS stops working, and class problem.



>   Yes, it is.  Netscape depends on Javascript to make CSS work.  It's a
>long story, but the short short version is that Netscape wanted to make
>styles and behaviors intertwined, but the W3C decided on a different path.

HWG hwg-style mailing list archives, maintained by Webmasters @ IWA