W3C home > Mailing lists > Public > www-style@w3.org > July 2005

[WF2] Readonly and default pseudoclass matching

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Tue, 26 Jul 2005 11:30:01 -0500
Message-ID: <42E66509.2080504@mit.edu>
To: whatwg@whatwg.org
CC: www-style Mailing List <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>

I have a question about the description of :read-only in WF2.  The description says:

   :read-only
     Matches form control elements that have the readonly attribute set, and to
     which the readonly attribute applies. (For instance, radio buttons will
     never match this, regardless of the value of the attribute.)

It's not clear to me whether this restricts :read-only to _only_ apply to those
form controls.  Per my reading of CSS3 UI, for example, :read-only should match
a random fieldset (since the fieldset itself is not editable in any way).  The
text in WF2 could be interpreted this way if one assumes that the whole of
section 8.2 only applies to "form controls" (that is, input, output, select,
textarea and button), but it's not completely clear what the spec is intending here.

Further, it would make sense to me if a disabled form control matched :readonly
(since it _is_ readonly; it doesn't so much matter how it got there, imo).  So
for example a disabled radio button would match readonly...

I also have a question about :default.  Again, CSS3 UI makes it pretty clear
that :default should match appropriate radio buttons, checkboxes, and options,
but WF2 says it only matches the default submit button.  I feel that this
contradiction should be somewhat clarified (probably by stating that :default
must match said submit button and may match other things as well, per CSS3 UI).

-Boris
Received on Tuesday, 26 July 2005 16:31:17 GMT

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