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

[whatwg] [WF2] Readonly and default pseudoclass matching

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Thu, 28 Jul 2005 19:49:51 -0500
Message-ID: <42E97D2F.1060101@mit.edu>
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.

Received on Thursday, 28 July 2005 17:49:51 UTC

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