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

Re: pseudo-attributes

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 29 Oct 2008 09:52:44 -0500
Message-ID: <dd0fbad0810290752i62b43cddm97c2b3b12f9fe866@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, "L. David Baron" <dbaron@dbaron.org>, www-style@w3.org
On Tue, Oct 28, 2008 at 6:24 PM, fantasai <fantasai.lists@inkedblade.net>wrote:

> Tab Atkins Jr. wrote:
>
>>
>> @David Baron:
>> The hint action can be done just as well with :empty:not(:focus).  Is
>> there a reasonable use-case that :empty doesn't solve equally well?
>>
>
> :empty checks for descendent nodes in the DOM tree. Given that <input>
> is an empty element, wouldn't it /always/ match an unfocused input field?
>
> ~fantasai


Sorry about that; I'm a crazy.  For some strange reason I thought :empty was
for text inputs.  In that case, I'd say [value=""], but that doesn't work.

Before creating an entirely new class of things, I'd just shoot for making
value update interactively.  If we can have :valid and :invalid update
interactively, surely we can have the same for [value].

(If not, the same can be achieved with a .+ @pattern and :invalid.)
Received on Wednesday, 29 October 2008 14:53:21 GMT

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