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

Re: Alternate stylesheets and the "disabled" DOM property

From: fantasai <fantasai@escape.com>
Date: Sat, 04 Oct 2003 01:54:35 -0400
Message-ID: <3F7E609B.7040004@escape.com>
To: www-style@w3.org

Chris Moschini wrote:
>> I don't think we want to get into selection persistence here.
>> That's done by the UA on behalf of the user,
> 
> Could the standard at least recommend something?

That's outside the domain of the specification; it's a user agent UI
design issue.

Now, if you're really interested in how it ought to be done, I can
do a writeup and post it here for discussion, but I don't think it
belongs in a W3C spec.

 > This is a problem with most present implementations; sure you can
 > pick a style, but if you did it in the UA, it's gone with the next
 > page click.

Like you said, that's a problem with the implementation, not the spec.
It's bug 83663 in Mozilla, and part of the reason it's not fixed is
because style switching is done via JavaScript and the DOM instead of
internally in the layout engine. Boris wants to change that, which is
why he posted here in the first place.

> If the standard at least suggested what entailed maintenance of style
> and what entailed ditching it, it would send UAs down a somewhat
> consistent path, but constrain any UA to that pattern alone in case
> they came up with something better (and in case of stepping on the
> toes of other standards...).

I'm not sure what you mean by this, but I don't think the spec needs to
constrain the UAs' style switching UI.

~fantasai
Received on Saturday, 4 October 2003 01:55:16 GMT

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