W3C home > Mailing lists > Public > www-style@w3.org > September 2003

Re: Alternate stylesheets and the "disabled" DOM property

From: Chris Moschini <cmoschini@myrealbox.com>
Date: Tue, 30 Sep 2003 10:03:50 -0400
To: www-style@w3.org
Message-ID: <1064930630.7b2d88e0cmoschini@myrealbox.com>

But Daniel, if a more powerful grouping mechanism already exists for stylesheets - @import - why group them again with the title attribute?

I absolutely agree that this use of "disabled" warps the attribute's purpose, but why not simply use a different, more appropriate attribute? What if for example, the rel attribute were alterred from "alternative stylesheet" to "preferred stylesheet"? What if we added a new attribute instead of misusing an existing one, such as render="true"?

Consider a scenario in which a webpage has several buttons strewn about (perhaps 5 in a toolbar) that, when clicked, toggle several Accessibility features: High-contrast colors, larger fonts, etc. Assume that implementing these features each requires applying a stylesheet; the DOM scripting required would be overkill.

How would you handle this scenario in method #2, when only 1 title may be set as the Active stylesheet? You cannot enable more than one alternative sheet, so for example, enabling high contrast fonts and large fonts are mutually exclusive.


-----Original Message-----
From: Daniel Glazman <danielglazman@easyconnect.fr>

I think approach #2 is more logical and in the end offers more control to both
the web author and the user on the document's rendering. I think approach #1 was
just a convenient hack, nobody was using the 'disabled' attribute anyway so why
not for style sets...




-Chris "SoopahMan" Moschini
http://hiveminds.info/
http://soopahman.com/
Received on Tuesday, 30 September 2003 10:03:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:23 GMT