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

Re: Selectors Tests

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 30 Oct 2008 15:18:58 -0700
Message-ID: <490A32D2.1040005@inkedblade.net>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
CC: Boris Zbarsky <bzbarsky@MIT.EDU>, www-style <www-style@w3.org>

Lachlan Hunt wrote:
> 
> Boris Zbarsky wrote:
>>
>> Lachlan Hunt wrote:
>>>   Most elements will be neither enabled nor disabled. An element is
>>>   enabled if the user can either activate it or transfer the focus to
>>>   it. An element is disabled if it could be enabled, but the user cannot
>>>   presently activate it or transfer focus to it.
>>
>> So should an <input type="text" style="display: none"> match 
>> :disabled, by that reasoning?
> 
> Clearly, the selector shouldn't be affected by the element's styling. But
> 
>> Note that I raised that exact question in 
>> https://bugzilla.mozilla.org/show_bug.cgi?id=410472
>>
>> I probably even agree that <input type="hidden"> shouldn't match 
>> :enabled/:disabled, but I think the Selectors text as it stands 
>> doesn't really say what we want it to say...
> 
> Agreed.

Well, the Selectors spec is fixable. Daniel and I are actively
editing it now. However I don't think I agree that :enabled/:disabled
should not apply to type="hidden". The distinction does exist for
hidden controls as well, does it not?

An interesting question would be what happens if I write
   input[type="hidden"] { display: inline; }
Would I get nothing? A readonly input control? Something else?

~fantasai
Received on Thursday, 30 October 2008 22:19:54 GMT

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