Re: Alternate stylesheets and the "disabled" DOM property

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 <>

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

Received on Tuesday, 30 September 2003 10:03:49 UTC