- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 11 Feb 2009 08:24:59 +0000 (UTC)
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Cc: fantasai <fantasai.lists@inkedblade.net>, www-style <www-style@w3.org>
On Wed, 29 Oct 2008, Lachlan Hunt wrote: > fantasai wrote: > > Lachlan Hunt wrote: > > > http://lachy.id.au/dev/css/tests/selectors/pseudo-classes/ui/ > > > > Interesting. I'm not convinced that :enabled and :disabled shouldn't match > > <input type="hidden">. Konqueror and Mozilla both make them match, so I'd > > like to check with the CSSWG if that's really the interpretation we want > > before deciding whether to accept your tests. > > Opera currently also makes them match, but WebKit doesn't. However, the > Selectors spec states that: > > 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. > > Since a hidden input cannot be activated or have focus transferred to it, my > understanding is that they shouldn't match, which makes WebKit's behaviour > correct, and Opera, Firefox and Konqueror all incorrect. But if the intention > is for these pseudo classes to match hidden inputs, then please fix the spec. > > > AFAICT WF2 requires them to match, but Selectors' wording implies that they > > don't. > > The Web Forms 2 spec is obsolete now that forms have been integrated into > HTML5. HTML5 now says :enabled never matches type=hidden. (And :disabled doesn't either, since you can't disable an <input type=hidden>.) -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 11 February 2009 08:25:34 UTC