- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 11 Feb 2009 23:42:57 +0000 (UTC)
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, www-style <www-style@w3.org>, whatwg@whatwg.org
On Wed, 11 Feb 2009, fantasai wrote: > > Given the state of current implementations and the fact that hidden input > elements do have distinct enabled and disabled states, I don't understand > the reasoning behind this change. > http://twitter.com/WHATWG/status/1198455588 The idea was to match Selectors. > On a related note, the HTML5 spec currently defines :enabled to match > <a>, <area>, and <link> elements, as well as any other elements that are > focusable--conflicting with the Selectors spec, which defines :enabled > to only apply to elements that have a corresponding disabled state. The spec text I read said "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.", which is what I tried to follow: http://www.w3.org/TR/css3-selectors/#UIstates > http://dev.w3.org/csswg/selectors3/#UIstates I see this has now changed. I will update HTML5 in due course to match the new text in Selectors. (I'll also update my spec index to point to the dev.w3.org link instead of the /TR/ page so that I don't make this mistake again.) Cheers, -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 11 February 2009 23:43:34 UTC