[whatwg] [wf2] 8.1. Relation to the CSS3 User Interface module

Ian Hickson ian at hixie.ch
Thu Oct 20 15:27:09 PDT 2005

On Tue, 22 Mar 2005, Anne van Kesteren wrote:
> :checked - according to Selectors this applies to HTML4 elements which 
> could have a SELECTED attribute, OPTION, a descendant from the SELECT or 
> DATALIST elements, is one of them, but is not listed.


> :indeterminate - I suggest that the wording is changed to say that it 
> does not match any Web Forms 2 form controls as Selectors seems to 
> suggest that it does match certain HTML controls in a certain state.


> :default - this psuedo-class should match more than just the inital submit
> button. (I assume it also matches when that button is disabled?) For example:
>  <select>
>   <option selected>foo
>   <option>bar
> The OPTION element with value "foo" should match :default as it is the default
> option in that form control. (When there is a <select multiple> more options
> could match :default.)


> A question about this, should it also match radio buttons where the author can
> also set a default out of multiple possibilities? (For checkboxes this does
> not apply I guess.)

Apparently so, yes.

> Also, how does :default work with non form controls. Would 
> 'html:not(:default){background:lime}' really give a green background in 
> HTML documents? (But perhaps this is something for CSS3 to clarify.) 
> (This question seems to apply to other pseudo-classes as well.)

If :checked doesn't match, :not(:checked) matches, this seems unambiguous.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list