W3C home > Mailing lists > Public > www-style@w3.org > November 2018

RE: [CSSWG][selectors-4] Updated WD of Selectors L4

From: Andrew Fedoniouk <andrew.fedoniouk@gmail.com>
Date: Wed, 21 Nov 2018 14:33:26 -0800
Message-ID: <5bf5dd39.1c69fb81.59d0b.7736@mx.google.com>
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>, "public-review-announce@w3.org" <public-review-announce@w3.org>, WHAT Working Group <whatwg@whatwg.org>
:blank is quite bad as a state name

For example <input type="text" value="">  shall be considered as not :blank as it has initial value deliberately set to blank string (empty string allowed).

I would suggest to use :undefined name instead with the following meaning:

:undefined is “on” for any <input> element that is not successful for submission at the moment [1] .  

[1] https://www.w3.org/TR/html401/interact/forms.html#h-17.13.2 

Andrew Fedoniouk

Terra Informatica Software, Inc.

Richmond, BC, Canada


From: fantasai
Sent: November 21, 2018 12:06 PM
To: www-style@w3.org; public-review-announce@w3.org; WHAT Working Group
Subject: [CSSWG][selectors-4] Updated WD of Selectors L4

The CSS WG has published an updated Working Draft of Selectors Level 4:


Selectors are patterns that match against elements in a tree and are used
as a core part of CSS and in DOM methods such as .querySelector()

This update adds, drops, and renames a number of selectors:
   * zero-specificity pseudo-class named :where()
   * :matches() renamed to :is()
   * :blank defined to select empty user input elements
   * :empty redefined to ignore whitespace-only text nodes
   * :drop() dropped due to removal of support in HTML
   * Added case-sensitive attribute value matching flag

In addition, the specificity rules for :is() and :nth-child() were altered
to use the most specific selector argument rather than the most specific
selector that happened to match. See
and discussion in

Changes since the February 2018 WD are all listed at:

One major issue that's open is redefining the way invalid selectors are
handled within `:is()` and similar pseudo-classes to ignore unknown
selectors rather than invalidating the entire style rule. See

Another series of open issues concerns the :visited pseudo-class and
how to balance security concerns with usability requirements. See e.g.

Please review the draft, and send any comments to the CSSWG mailing list,
<www-style@w3.org>, prefixed with [selectors-4] (as I did on this
message) or (preferably) file them in the GitHub repository at

For the CSS WG,
Received on Wednesday, 21 November 2018 22:33:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:12 UTC