W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2005

[whatwg] [WF2] Readonly and default pseudoclass matching

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 29 Jul 2005 00:58:53 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0507290057010.4466@dhalsim.dreamhost.com>
On Thu, 28 Jul 2005, Boris Zbarsky wrote:
>
> Ian Hickson wrote:
> > Well, properties sheets in Windows have that kind of UI, for instance. But
> > even if that was not the case, what is the use case for _not_ doing this? 
> 
> The use case is being able to style things based on whether the user can 
> edit them, no matter what the reason is for the user to not edit them.  
> Right now, for that use case you'd have to have to have 
> "selector:disabled, selector:read-only", which is rather 
> counter-intuitive.

Sure, just like styling every link requires "selector:link, 
selector:visited". But that is better than preventing the alternative, in 
my opinion.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 28 July 2005 17:58:53 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:42 UTC