W3C home > Mailing lists > Public > www-style@w3.org > March 2012

[selectors4] :empty psuedo class and input fields

From: Stefan Wallin <Stefan.W@festiz.com>
Date: Sun, 11 Mar 2012 00:10:50 +0100
Message-ID: <CA+9vH7AdbFsxQBeJGXQPn_Sq=nWJ0LdDRqL-otKNNk+28mUMmg@mail.gmail.com>
To: www-style@w3.org
Hi all!

This is my first attempt to contribute to the world of standards, so bare
with me. If I'm not doing this the proper way, please tell me.

My issue. I think the :empty pseudo class selector is not super intuitive
when it comes to form elements such as input fields.


Both Selectors 3 and Selectors 4 states the following:

> The :empty pseudo-class represents an element that has no children at
> all. In terms of the document tree, only element nodes and content nodes
> (such as DOM [DOM-LEVEL-3-CORE]<http://www.w3.org/TR/selectors/#DOM-LEVEL-3-CORE> text
> nodes, CDATA nodes, and entity references) whose data has a non-zero length
> must be considered as affecting emptiness; comments, processing
> instructions, and other nodes must not affect whether an element is
> considered empty or not.


This strikes a chord with me, I'd really like to see the possibility to
style input fields that do not fit to be classed as required but are still
empty to be styled differently. Today this has to be done with DOM
scripting, neither input[value=""] or input:empty works as I think it
should work.

input:empty always marks as true, regardless if the value attribute is
empty or not.

input[value=""] only detects initial status and not changes to the element
later on in the page lifetime.

Should one not be able to check the content of the DOM attr value
dynamically through CSS?

Humbly

Stefan Wallin
================================
+46 (0) 709-529 036 || stefan.w@festiz.com
http://www.stefan-wallin.se
http://twitter.com/Stefan_Wallin
Received on Monday, 12 March 2012 14:00:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:48:51 GMT