Selectors Level 4
Selectors Level 4
W3C Working Draft
22 January 2026
More details about this document
This version:
Latest published version:
Editor's Draft:
Previous Versions:
History:
Feedback:
CSSWG Issues Repository
Inline In Spec
Editors:
Elika J. Etemad / fantasai
Apple
Tab Atkins Jr.
Google
Former Editors:
Tantek Çelik
Daniel Glazman
Ian Hickson
Peter Linss
John Williams
Suggest an Edit for this Spec:
GitHub Editor
Test Suite:
World Wide Web Consortium
W3C
liability
trademark
and
permissive document license
rules apply.
Abstract
Selectors
are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select nodes in a document. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code. They are a core component of
CSS
(Cascading Style Sheets), which uses Selectors to bind style properties to elements in the document.
Selectors Level 4 describes the selectors that already exist in
[SELECT]
, and further introduces new selectors for CSS and other languages that may need them.
CSS
is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, etc.
Status of this document
This section describes the status of this document at the time of its publication.
A list of current W3C publications
and the latest revision of this technical report
can be found in the
W3C standards and drafts index.
This document was published
by the
CSS Working Group
as a
Working Draft
using the
Recommendation
track
Publication as a Working Draft
does not imply endorsement by
W3C
and its Members.
This is a draft document
and may be updated, replaced
or obsoleted by other documents at any time.
It is inappropriate to cite this document as other than a work in progress.
Please send feedback
by
filing issues in GitHub
(preferred),
including the spec code “selectors” in the title, like this:
“[selectors]
…summary of comment…
”.
All issues and comments are
archived
Alternately, feedback can be sent to the (
archived
) public mailing list
www-style@w3.org
This document is governed by the
18 August 2025 W3C Process Document
This document was produced by a group operating under the
W3C Patent Policy
W3C maintains a
public list of any patent disclosures
made in connection with the deliverables of the group;
that page also includes instructions for disclosing a patent.
An individual who has actual knowledge of a patent that the individual believes
contains
Essential Claim(s)
must disclose the information in accordance with
section 6 of the W3C Patent Policy
The following features are at-risk, and may be dropped during the CR period:
the column combinator
user action pseudo-classes
applying to non-
tree-abiding pseudo-elements
“At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first.
1.
Introduction
This section is not normative.
Tests
This section is not normative, it does not need tests.
selector
is a boolean predicate
that takes an element in a tree structure
and tests whether the element matches the selector or not.
These expressions may be used for many things:
directly on an element to test whether it matches some criteria,
such as in the
element.matches()
function defined in
[DOM]
applied to an entire tree of elements
to filter it into a set of elements that match the criteria,
such as in the
document.querySelectorAll()
function defined in
[DOM]
or the selector of a CSS style rule.
used "in reverse" to generate markup that would match a given selector,
such as in
HAML
or
Emmet
Selectors Levels 1, 2, and 3 are defined as the subsets of selector
functionality defined in the
CSS1
CSS2.1
, and
Selectors Level 3
specifications, respectively. This module defines Selectors Level 4.
1.1.
Module Interactions
Tests
Tests not needed for this section.
This module replaces the definitions of
and extends the set of selectors defined for CSS in
[SELECT]
and
[CSS21]
Pseudo-element selectors,
which define abstract elements in a rendering tree,
are not part of this specification:
their generic syntax is described here,
but, due to their close integration with the rendering model and irrelevance to other uses such as DOM queries,
they will be defined in other modules.
2.
Selectors Overview
This section is non-normative, as it merely summarizes the
following sections.
Tests
This section is not normative, it does not need tests.
A selector represents a structure. This structure can be used as a
condition (e.g. in a CSS rule) that determines which elements a
selector matches in the document tree, or as a flat description of the
HTML or XML fragment corresponding to that structure.
Selectors may range from simple element names to rich contextual
representations.
The following table summarizes the Selector syntax:
Pattern
Represents
Section
Level
any element
§ 5.2 Universal selector
an element of type E
§ 5.1 Type (tag name) selector
E:not(
s1
s2
, …)
an E element that does not match either
compound selector
s1
or
compound selector
s2
§ 4.3 The Negation (Matches-None) Pseudo-class: :not()
3/4
E:is(
s1
s2
, …)
an E element that matches
compound selector
s1
and/or
compound selector
s2
§ 4.2 The Matches-Any Pseudo-class: :is()
E:where(
s1
s2
, …)
an E element that matches
compound selector
s1
and/or
compound selector
s2
but contributes no specificity.
§ 4.4 The Specificity-adjustment Pseudo-class: :where()
E:has(
rs1
rs2
, …)
an E element,
if there exists an element that matches
either of the
relative selectors
rs1
or
rs2
when evaluated with E as the
anchor elements
§ 4.5 The Relational Pseudo-class: :has()
E.warning
an E element belonging to the class
warning
(the document language specifies how class is determined).
§ 6.6 Class selectors
E#myid
an E element with ID equal to
myid
§ 6.7 ID selectors
E[foo]
an E element with a
foo
attribute
§ 6.1 Attribute presence and value selectors
E[foo="bar"]
an E element whose
foo
attribute value is
exactly equal to
bar
§ 6.1 Attribute presence and value selectors
E[foo="bar" i]
an E element whose
foo
attribute value is
exactly equal to any (ASCII-range) case-permutation of
bar
§ 6.3 Case-sensitivity
E[foo="bar" s]
an E element whose
foo
attribute value is
identical to
bar
§ 6.3 Case-sensitivity
E[foo~="bar"]
an E element whose
foo
attribute value is
a list of whitespace-separated values, one of which is
exactly equal to
bar
§ 6.1 Attribute presence and value selectors
E[foo^="bar"]
an E element whose
foo
attribute value
begins exactly with the string
bar
§ 6.2 Substring matching attribute selectors
E[foo$="bar"]
an E element whose
foo
attribute value
ends exactly with the string
bar
§ 6.2 Substring matching attribute selectors
E[foo*="bar"]
an E element whose
foo
attribute value
contains the substring
bar
§ 6.2 Substring matching attribute selectors
E[foo|="en"]
an E element whose
foo
attribute value is
a hyphen-separated list of values beginning with
en
§ 6.1 Attribute presence and value selectors
E:dir(ltr)
an element of type E with left-to-right directionality
(the document language specifies how directionality is determined)
§ 7.1 The Directionality Pseudo-class: :dir()
E:lang(zh, "*-hant")
an element of type E tagged as being either in Chinese
(any dialect or writing system)
or otherwise written with traditional Chinese characters
§ 7.2 The Language Pseudo-class: :lang()
2/4
E:any-link
an E element being the source anchor of a hyperlink
§ 8.1 The Hyperlink Pseudo-class: :any-link
E:link
an E element being the source anchor of a hyperlink
of which the target is not yet visited
§ 8.2 The Link History Pseudo-classes: :link and :visited
E:visited
an E element being the source anchor of a hyperlink
of which the target is already visited
§ 8.2 The Link History Pseudo-classes: :link and :visited
E:target
an E element being the target of the current URL
§ 8.3 The Target Pseudo-class: :target
E:scope
an E element being a
scoping root
§ 8.4 The Reference Element Pseudo-class: :scope
E:active
an E element that is in an activated state
§ 9.2 The Activation Pseudo-class: :active
E:hover
an E element that is under the cursor,
or that has a descendant under the cursor
§ 9.1 The Pointer Hover Pseudo-class: :hover
E:focus
an E element that has user input focus
§ 9.3 The Input Focus Pseudo-class: :focus
E:focus-within
an E element that has user input focus or contains an element that has input focus.
§ 9.5 The Focus Container Pseudo-class: :focus-within
E:focus-visible
an E element that has user input focus,
and the UA has determined that a focus ring or other indicator
should be drawn for that element
§ 9.4 The Focus-Indicated Pseudo-class: :focus-visible
E:enabled
E:disabled
a user interface element E that is enabled or disabled, respectively
§ 12.1.1 The :enabled and :disabled Pseudo-classes
E:read-write
E:read-only
a user interface element E that is user alterable, or not
§ 12.1.2 The Mutability Pseudo-classes: :read-only and :read-write
3-UI/4
E:placeholder-shown
an input control currently showing placeholder text
§ 12.1.3 The Placeholder-shown Pseudo-class: :placeholder-shown
3-UI/4
E:default
a user interface element E that is the default item in a group of related choices
§ 12.1.5 The Default-option Pseudo-class: :default
3-UI/4
E:checked
E:unchecked
E:indeterminate
a user interface element E that is checked/selected
(for instance a radio-button or checkbox),
unchecked,
or in an indeterminate state
(neither checked nor unchecked)
§ 12.2 Input Value States
E:valid
E:invalid
a user-input element E that meets, or doesn’t, its data validity semantics
§ 12.3.1 The Validity Pseudo-classes: :valid and :invalid
3-UI/4
E:in-range
E:out-of-range
a user-input element E whose value is in-range/out-of-range
§ 12.3.2 The Range Pseudo-classes: :in-range and :out-of-range
3-UI/4
E:required
E:optional
a user-input element E that requires/does not require input
§ 12.3.3 The Optionality Pseudo-classes: :required and :optional
3-UI/4
E:user-invalid
a user-altered user-input element E with incorrect input (invalid, out-of-range, omitted-but-required)
§ 12.3.4 The User-interaction Pseudo-classes: :user-valid and :user-invalid
E:root
an E element, root of the document
§ 13.1 :root pseudo-class
E:empty
an E element that has no children (neither elements nor text) except perhaps white space
§ 13.2 :empty pseudo-class
E:nth-child(
[of
]?)
an E element, the
-th child of its parent matching
§ 13.3.1 :nth-child() pseudo-class
3/4
E:nth-last-child(
[of
]?)
an E element, the
-th child of its parent matching
counting from the last one
§ 13.3.2 :nth-last-child() pseudo-class
3/4
E:first-child
an E element, first child of its parent
§ 13.3.3 :first-child pseudo-class
E:last-child
an E element, last child of its parent
§ 13.3.4 :last-child pseudo-class
E:only-child
an E element, only child of its parent
§ 13.3.5 :only-child pseudo-class
E:nth-of-type(
an E element, the
-th sibling of its type
§ 13.4.1 :nth-of-type() pseudo-class
E:nth-last-of-type(
an E element, the
-th sibling of its type,
counting from the last one
§ 13.4.2 :nth-last-of-type() pseudo-class
E:first-of-type
an E element, first sibling of its type
§ 13.4.3 :first-of-type pseudo-class
E:last-of-type
an E element, last sibling of its type
§ 13.4.4 :last-of-type pseudo-class
E:only-of-type
an E element, only sibling of its type
§ 13.4.5 :only-of-type pseudo-class
E F
an F element descendant of an E element
§ 14.1 Descendant combinator ( )
E > F
an F element child of an E element
§ 14.2 Child combinator (>)
E + F
an F element immediately preceded by an E element
§ 14.3 Next-sibling combinator (+)
E ~ F
an F element preceded by an E element
§ 14.4 Subsequent-sibling combinator (~)
Note:
Some Level 4 selectors (noted above as "3-UI") were introduced in
[CSS3UI]
Tests
css3-modsel-1.xml (visual test)
(source)
css3-modsel-10.xml (visual test)
(source)
css3-modsel-100.xml (visual test)
(source)
css3-modsel-100b.xml (visual test)
(source)
css3-modsel-101.xml
(live test)
(source)
css3-modsel-101b.xml
(live test)
(source)
css3-modsel-102.xml
(live test)
(source)
css3-modsel-102b.xml (visual test)
(source)
css3-modsel-103.xml
(live test)
(source)
css3-modsel-103b.xml
(live test)
(source)
css3-modsel-104.xml (visual test)
(source)
css3-modsel-104b.xml (visual test)
(source)
css3-modsel-105.xml
(live test)
(source)
css3-modsel-105b.xml
(live test)
(source)
css3-modsel-106.xml
(live test)
(source)
css3-modsel-106b.xml
(live test)
(source)
css3-modsel-107.xml (visual test)
(source)
css3-modsel-107b.xml (visual test)
(source)
css3-modsel-108.xml
(live test)
(source)
css3-modsel-108b.xml
(live test)
(source)
css3-modsel-109.xml
(live test)
(source)
css3-modsel-109b.xml
(live test)
(source)
css3-modsel-11.xml (visual test)
(source)
css3-modsel-110.xml
(live test)
(source)
css3-modsel-110b.xml
(live test)
(source)
css3-modsel-111.xml (visual test)
(source)
css3-modsel-111b.xml (visual test)
(source)
css3-modsel-112.xml
(live test)
(source)
css3-modsel-112b.xml
(live test)
(source)
css3-modsel-113.xml (visual test)
(source)
css3-modsel-113b.xml (visual test)
(source)
css3-modsel-114.xml (visual test)
(source)
css3-modsel-114b.xml (visual test)
(source)
css3-modsel-115.xml
(live test)
(source)
css3-modsel-115b.xml
(live test)
(source)
css3-modsel-116.xml
(live test)
(source)
css3-modsel-116b.xml
(live test)
(source)
css3-modsel-117.xml
(live test)
(source)
css3-modsel-117b.xml
(live test)
(source)
css3-modsel-118.xml (visual test)
(source)
css3-modsel-119.xml (visual test)
(source)
css3-modsel-120.xml (visual test)
(source)
css3-modsel-121.xml (visual test)
(source)
css3-modsel-122.xml
(live test)
(source)
css3-modsel-123.xml (visual test)
(source)
css3-modsel-123b.xml (visual test)
(source)
css3-modsel-124.xml (visual test)
(source)
css3-modsel-124b.xml (visual test)
(source)
css3-modsel-125.xml
(live test)
(source)
css3-modsel-125b.xml
(live test)
(source)
css3-modsel-126.xml
(live test)
(source)
css3-modsel-126b.xml
(live test)
(source)
css3-modsel-127.xml
(live test)
(source)
css3-modsel-127b.xml
(live test)
(source)
css3-modsel-128.xml
(live test)
(source)
css3-modsel-128b.xml
(live test)
(source)
css3-modsel-129.xml
(live test)
(source)
css3-modsel-129b.xml
(live test)
(source)
css3-modsel-13.xml (visual test)
(source)
css3-modsel-130.xml (visual test)
(source)
css3-modsel-130b.xml (visual test)
(source)
css3-modsel-131.xml (visual test)
(source)
css3-modsel-131b.xml (visual test)
(source)
css3-modsel-132.xml (visual test)
(source)
css3-modsel-132b.xml (visual test)
(source)
css3-modsel-133.xml (visual test)
(source)
css3-modsel-133b.xml (visual test)
(source)
css3-modsel-134.xml
(live test)
(source)
css3-modsel-134b.xml
(live test)
(source)
css3-modsel-135.xml
(live test)
(source)
css3-modsel-135b.xml
(live test)
(source)
css3-modsel-136.xml
(live test)
(source)
css3-modsel-136b.xml
(live test)
(source)
css3-modsel-137.xml (visual test)
(source)
css3-modsel-137b.xml (visual test)
(source)
css3-modsel-138.xml (visual test)
(source)
css3-modsel-138b.xml (visual test)
(source)
css3-modsel-139.xml (visual test)
(source)
css3-modsel-139b.xml (visual test)
(source)
css3-modsel-14.xml (visual test)
(source)
css3-modsel-140.xml (visual test)
(source)
css3-modsel-140b.xml (visual test)
(source)
css3-modsel-141.xml
(live test)
(source)
css3-modsel-141b.xml
(live test)
(source)
css3-modsel-142.xml
(live test)
(source)
css3-modsel-142b.xml
(live test)
(source)
css3-modsel-143.xml
(live test)
(source)
css3-modsel-143b.xml
(live test)
(source)
css3-modsel-144.xml (visual test)
(source)
css3-modsel-145a.xml (visual test)
(source)
css3-modsel-145b.xml (visual test)
(source)
css3-modsel-146a.xml (visual test)
(source)
css3-modsel-146b.xml (visual test)
(source)
css3-modsel-147a.xml (visual test)
(source)
css3-modsel-147b.xml (visual test)
(source)
css3-modsel-148.xml
(live test)
(source)
css3-modsel-149.xml
(live test)
(source)
css3-modsel-149b.xml
(live test)
(source)
css3-modsel-14b.xml
(live test)
(source)
css3-modsel-14c.xml (visual test)
(source)
css3-modsel-14d.xml (visual test)
(source)
css3-modsel-14e.xml (visual test)
(source)
css3-modsel-15.xml (visual test)
(source)
css3-modsel-150.xml (visual test)
(source)
css3-modsel-151.xml
(live test)
(source)
css3-modsel-152.xml
(live test)
(source)
css3-modsel-153.xml (visual test)
(source)
css3-modsel-154.xml
(live test)
(source)
css3-modsel-155.xml
(live test)
(source)
css3-modsel-155a.xml
(live test)
(source)
css3-modsel-155b.xml
(live test)
(source)
css3-modsel-155c.xml
(live test)
(source)
css3-modsel-155d.xml
(live test)
(source)
css3-modsel-156.xml
(live test)
(source)
css3-modsel-156b.xml
(live test)
(source)
css3-modsel-156c.xml
(live test)
(source)
css3-modsel-157.xml
(live test)
(source)
css3-modsel-158.xml
(live test)
(source)
css3-modsel-159.xml (manual test)
(source)
css3-modsel-15b.xml
(live test)
(source)
css3-modsel-16.xml (manual test)
(source)
css3-modsel-160.xml
(live test)
(source)
css3-modsel-161.xml (manual test)
(source)
css3-modsel-166.xml (visual test)
(source)
css3-modsel-166a.xml (visual test)
(source)
css3-modsel-167.xml (visual test)
(source)
css3-modsel-167a.xml (visual test)
(source)
css3-modsel-168.xml
(live test)
(source)
css3-modsel-168a.xml
(live test)
(source)
css3-modsel-169.xml
(live test)
(source)
css3-modsel-169a.xml
(live test)
(source)
css3-modsel-17.xml (manual test)
(source)
css3-modsel-170.xml
(live test)
(source)
css3-modsel-170a.xml
(live test)
(source)
css3-modsel-170b.xml
(live test)
(source)
css3-modsel-170c.xml
(live test)
(source)
css3-modsel-170d.xml
(live test)
(source)
css3-modsel-171.xml (visual test)
(source)
css3-modsel-172a.xml
(live test)
(source)
css3-modsel-172b.xml
(live test)
(source)
css3-modsel-173a.xml
(live test)
(source)
css3-modsel-173b.xml
(live test)
(source)
css3-modsel-174a.xml (visual test)
(source)
css3-modsel-174b.xml (visual test)
(source)
css3-modsel-175a.xml
(live test)
(source)
css3-modsel-175b.xml
(live test)
(source)
css3-modsel-175c.xml
(live test)
(source)
css3-modsel-176.xml
(live test)
(source)
css3-modsel-177a.xml (manual test)
(source)
css3-modsel-177b.xml
(live test)
(source)
css3-modsel-178.xml
(live test)
(source)
css3-modsel-179.xml
(live test)
(source)
css3-modsel-179a.xml (visual test)
(source)
css3-modsel-18.xml (manual test)
(source)
css3-modsel-180a.xml (visual test)
(source)
css3-modsel-181.xml (visual test)
(source)
css3-modsel-182.xml (visual test)
(source)
css3-modsel-183.xml (visual test)
(source)
css3-modsel-184a.xml
(live test)
(source)
css3-modsel-184b.xml
(live test)
(source)
css3-modsel-184c.xml
(live test)
(source)
css3-modsel-184d.xml
(live test)
(source)
css3-modsel-184e.xml
(live test)
(source)
css3-modsel-184f.xml
(live test)
(source)
css3-modsel-18a.xml (manual test)
(source)
css3-modsel-18b.xml (manual test)
(source)
css3-modsel-18c.xml (manual test)
(source)
css3-modsel-19.xml (manual test)
(source)
css3-modsel-19b.xml (manual test)
(source)
css3-modsel-2.xml (visual test)
(source)
css3-modsel-20.xml (manual test)
(source)
css3-modsel-21.xml (manual test)
(source)
css3-modsel-21b.xml (visual test)
(source)
css3-modsel-21c.xml (visual test)
(source)
css3-modsel-22.xml (visual test)
(source)
css3-modsel-25.xml (visual test)
(source)
css3-modsel-27.xml (visual test)
(source)
css3-modsel-27a.xml (visual test)
(source)
css3-modsel-27b.xml (visual test)
(source)
css3-modsel-28.xml (visual test)
(source)
css3-modsel-28b.xml (visual test)
(source)
css3-modsel-29.xml (visual test)
(source)
css3-modsel-29b.xml (visual test)
(source)
css3-modsel-3.xml (visual test)
(source)
css3-modsel-30.xml (visual test)
(source)
css3-modsel-31.xml (visual test)
(source)
css3-modsel-32.xml (visual test)
(source)
css3-modsel-33.xml (visual test)
(source)
css3-modsel-34.xml (visual test)
(source)
css3-modsel-35.xml (visual test)
(source)
css3-modsel-36.xml (visual test)
(source)
css3-modsel-37.xml (visual test)
(source)
css3-modsel-38.xml (visual test)
(source)
css3-modsel-39.xml (visual test)
(source)
css3-modsel-39a.xml (visual test)
(source)
css3-modsel-39b.xml (visual test)
(source)
css3-modsel-39c.xml (visual test)
(source)
css3-modsel-3a.xml (visual test)
(source)
css3-modsel-4.xml (visual test)
(source)
css3-modsel-41.xml (visual test)
(source)
css3-modsel-41a.xml (visual test)
(source)
css3-modsel-42.xml (visual test)
(source)
css3-modsel-42a.xml (visual test)
(source)
css3-modsel-43.xml (visual test)
(source)
css3-modsel-43b.xml (visual test)
(source)
css3-modsel-44.xml (visual test)
(source)
css3-modsel-44b.xml (visual test)
(source)
css3-modsel-44c.xml (visual test)
(source)
css3-modsel-44d.xml (visual test)
(source)
css3-modsel-45.xml (visual test)
(source)
css3-modsel-45b.xml (visual test)
(source)
css3-modsel-45c.xml (visual test)
(source)
css3-modsel-46.xml (visual test)
(source)
css3-modsel-46b.xml (visual test)
(source)
css3-modsel-47.xml (visual test)
(source)
css3-modsel-48.xml
(live test)
(source)
css3-modsel-49.xml
(live test)
(source)
css3-modsel-5.xml (visual test)
(source)
css3-modsel-50.xml (visual test)
(source)
css3-modsel-51.xml (visual test)
(source)
css3-modsel-52.xml (visual test)
(source)
css3-modsel-53.xml (visual test)
(source)
css3-modsel-54.xml
(live test)
(source)
css3-modsel-55.xml
(live test)
(source)
css3-modsel-56.xml
(live test)
(source)
css3-modsel-57.xml (visual test)
(source)
css3-modsel-57b.xml (visual test)
(source)
css3-modsel-59.xml
(live test)
(source)
css3-modsel-6.xml (visual test)
(source)
css3-modsel-60.xml
(live test)
(source)
css3-modsel-61.xml (manual test)
(source)
css3-modsel-62.xml (manual test)
(source)
css3-modsel-63.xml (manual test)
(source)
css3-modsel-64.xml (manual test)
(source)
css3-modsel-65.xml (manual test)
(source)
css3-modsel-66.xml (manual test)
(source)
css3-modsel-66b.xml (visual test)
(source)
css3-modsel-67.xml (visual test)
(source)
css3-modsel-7.xml (visual test)
(source)
css3-modsel-70.xml (visual test)
(source)
css3-modsel-72.xml (visual test)
(source)
css3-modsel-72b.xml (visual test)
(source)
css3-modsel-73.xml (visual test)
(source)
css3-modsel-73b.xml (visual test)
(source)
css3-modsel-74.xml (visual test)
(source)
css3-modsel-74b.xml (visual test)
(source)
css3-modsel-75.xml (visual test)
(source)
css3-modsel-75b.xml (visual test)
(source)
css3-modsel-76.xml (visual test)
(source)
css3-modsel-76b.xml (visual test)
(source)
css3-modsel-77.xml (visual test)
(source)
css3-modsel-77b.xml (visual test)
(source)
css3-modsel-78.xml (visual test)
(source)
css3-modsel-78b.xml (visual test)
(source)
css3-modsel-79.xml (visual test)
(source)
css3-modsel-7b.xml
(live test)
(source)
css3-modsel-8.xml (visual test)
(source)
css3-modsel-80.xml (visual test)
(source)
css3-modsel-81.xml (visual test)
(source)
css3-modsel-81b.xml (visual test)
(source)
css3-modsel-82.xml (visual test)
(source)
css3-modsel-82b.xml (visual test)
(source)
css3-modsel-83.xml
(live test)
(source)
css3-modsel-86.xml (visual test)
(source)
css3-modsel-87.xml
(live test)
(source)
css3-modsel-87b.xml
(live test)
(source)
css3-modsel-88.xml (visual test)
(source)
css3-modsel-88b.xml (visual test)
(source)
css3-modsel-89.xml (visual test)
(source)
css3-modsel-9.xml (visual test)
(source)
css3-modsel-90.xml
(live test)
(source)
css3-modsel-90b.xml
(live test)
(source)
css3-modsel-91.xml (visual test)
(source)
css3-modsel-92.xml (visual test)
(source)
css3-modsel-93.xml (visual test)
(source)
css3-modsel-94.xml (visual test)
(source)
css3-modsel-94b.xml (visual test)
(source)
css3-modsel-95.xml (visual test)
(source)
css3-modsel-96.xml (visual test)
(source)
css3-modsel-96b.xml (visual test)
(source)
css3-modsel-97.xml (visual test)
(source)
css3-modsel-97b.xml (visual test)
(source)
css3-modsel-98.xml (visual test)
(source)
css3-modsel-98b.xml (visual test)
(source)
css3-modsel-99.xml
(live test)
(source)
css3-modsel-99b.xml
(live test)
(source)
css3-modsel-d1.xml (visual test)
(source)
css3-modsel-d1b.xml (visual test)
(source)
css3-modsel-d2.xml (visual test)
(source)
css3-modsel-d3.xml (visual test)
(source)
css3-modsel-d4.xml (visual test)
(source)
Tests that do not relate to any section
eof-right-after-selector-crash.html
(live test)
(source)
eof-some-after-selector-crash.html
(live test)
(source)
hash-collision.html
(live test)
(source)
invalid-pseudos.html
(live test)
(source)
selector-after-font-family.html
(live test)
(source)
3.
Selector Syntax and Structure
3.1.
Structure and Terminology
selector
represents
a particular pattern of element(s) in a tree structure.
The term
selector
can refer to a
simple selector
compound selector
complex selector
, or
selector list
The
subject of a selector
is
any element that selector is defined to be about;
that is, any element
matching
that
selector
simple selector
is a single condition on an element.
type selector
universal selector
attribute selector
class selector
ID selector
or
pseudo-class
is a
simple selector
(It is represented by
in the selectors
grammar
.)
A given element is said to
match
simple selector
when that
simple selector
as defined in this specification and in accordance with the
document language
accurately describes the element.
compound selector
is a sequence of
simple selectors
that are not separated by a
combinator
and represents a set of simultaneous conditions on a single element.
If it contains a
type selector
or
universal selector
that selector must come first in the sequence.
Only one type selector or universal selector is allowed in the sequence.
(A
compound selector
is represented by
in the selectors
grammar
.)
A given element is said to
match
compound selector
when it matches all
simple selectors
in the
compound selector
Note:
As whitespace represents the
descendant combinator
no whitespace is allowed between the
simple selectors
in a
compound selector
pseudo-compound selector
is a
pseudo-element
selector,
optionally followed by additional
pseudo-class
selectors,
and optionally preceded by a
compound selector
or another
pseudo-compound selector
without any
combinators
(A
pseudo-compound selector
is represented by
in the selectors
grammar
.)
pseudo-element
matches
pseudo-compound selector
when it has the specified pseudo-element name,
matches the additional conditions represented by any
pseudo-classes
and has an
originating element
represented by the adjacent preceding selector.
If there is no adjacent preceding selector,
the
universal selector
is assumed.
(For example,
.foo ::before
is equivalent to
.foo *::before
and distinct from
.foo::before
.)
For example, in
.foo::before:hover
the
.foo
is a
compound selector
while the
::before:hover
is a
pseudo-compound selector
However, in
.foo::before::marker
::before
and
::marker
are separate
pseudo-compound selectors
Note:
pseudo-compound selector
is not
compound selector
and can’t be used in places that expect a
compound selector
only.
Pseudo-compound selectors
act as if they carry a
combinator
with themselves,
expressing their relationship with their
originating element
just as the
combinator
expresses a relationship with a parent element.
combinator
is a condition of relationship between two elements
represented by the
compound selectors
on either side.
Combinators in Selectors Level 4 include:
the
descendant combinator
(white space),
the
child combinator
(U+003E,
),
the
next-sibling combinator
(U+002B,
),
and the
subsequent-sibling combinator
(U+007E,
).
Two given elements are said to
match
combinator
when the condition of relationship between these elements is true.
complex selector
is
a sequence of one or more
compound selectors
and/or
pseudo-compound selectors
with
compound selectors
separated by
combinators
It represents a set of simultaneous conditions
on a set of elements in the particular relationships
described by its
combinators
(Complex selectors are represented by
in the selectors
grammar
.)
A given element or pseudo-element
is said to
match
complex selector
when it matches the final
compound
pseudo-compound selector
in the sequence,
and every preceding unit of the sequence also
matches
an element or
pseudo-element
with the correct relationship between consecutive units
as expressed by the combinators separating them
(or, for
pseudo-compound selectors
the correct
originating element
relationship).
For example,
.foo.bar
matches an element
with both "foo" and "bar" classes.
.ancestor > .foo.bar
matches a subset of those elements:
only those whose parent element
(as indicated by the
combinator)
has the "ancestor" class.
.foo.bar::before
matches a
::before
pseudo-element,
whose
originating element
matches
.foo.bar
list of simple/compound/complex selectors
is a comma-separated list of
simple
compound
or
complex selectors
This is also called just a
selector list
when the type is either unimportant or specified in the surrounding prose;
if the type is important and unspecified,
it defaults to meaning a
list of complex selectors
(See
§ 4.1 Selector Lists
for additional information on
selector lists
and the various <*-selector-list> productions in the
grammar
for their formal syntax.)
A given element is said to
match
selector list
when it matches any (at least one) of the
selectors
in that
selector list
3.2.
Data Model
Selectors are evaluated against an element tree such as the DOM.
[DOM]
Within this specification,
this may be referred to as the "document tree" or "source document".
Each element may have any of the following five aspects,
which can be selected against,
all of which are matched as strings:
The element’s type (also known as its tag name).
The element’s namespace.
An ID.
Classes (named groups) to which it belongs.
Attributes, which are name-value pairs.
Many of the selectors depend on the semantics of the
document language
(i.e. the language and semantics of the document tree)
and/or the semantics of the
host language
(i.e. the language that is using selectors syntax).
For example, the
:lang()
selector depends on the
document language
(e.g. HTML)
to define how an element is associated with a language.
As a slightly different example, the
::first-line
pseudo-element
depends on the
host language
(e.g. CSS)
to define what a
::first-line
pseudo-element represents
and what it can do.
3.2.1.
Featureless Elements
Tests
featureless-001.html
(live test)
(source)
featureless-002.html
(live test)
(source)
featureless-003.html
(live test)
(source)
featureless-004.html
(live test)
(source)
featureless-005.html
(live test)
(source)
While individual elements may lack any of the above features,
some elements are
featureless
featureless
element does not match
any selector at all
except:
simple selectors
it is explicitly defined to match
compound selectors
if all contained
simple selectors
are allowed to match it
complex selectors
if the
compound selector
targeting the
subject
is allowed to match it
selector lists
if at least one selector in the list
is allowed to match it
logical combination pseudo-classes
if their argument selector is allowed to match it
the
:has()
pseudo-class,
if and only if the
compound selector
it’s part of
contains at least one
other
simple selector
that’s allowed to match it.
If a selector would otherwise match a
featureless
element,
except for the existence of the default namespace
[CSS-NAMESPACES-3]
(because
featureless
elements do not have a namespace
unless otherwise defined),
the default namespace does not prevent the match.
For example, the
shadow host
in a
shadow tree
is
featureless
and can’t be matched by
any
pseudo-class
except for
:host
and
:host-context()
(or combinations including those,
such as
:is(:host, :root)
).
Logical combinations like
:not(.foo:host)
will never match the host element
(even if it doesn’t have a "foo" class),
because not all of the simple selectors in
.foo:host
are allowed to match the
shadow host
Similarly,
:not(:host > .foo)
will never match the
shadow host
even tho the
shadow host
is indeed *not* a descendant of itself
and doesn’t have the "foo" class,
because the subject of the complex selector argument (
.foo
isn’t allowed to match the
shadow host
In general, you can’t match a
featureless
element
without explicitly using one of the
simple selectors
it’s allowed to match,
to avoid accidentally selecting one of these elements
(which are otherwise
intentionally
easy to not think about).
For example,
will never match a
featureless
element.
The rule for
:has()
, above, works similarly.
Even if a
shadow host
contains a
.foo
descendant,
:has(.foo)
will not match it,
because
the rest
of the compound selector
(empty)
doesn’t contain a simple selector that can match the host.
You have to write
:host:has(.foo)
in order to match the host element.
3.3.
Scoped Selectors
Some host applications may choose to
scope
selectors
to a particular subtree or fragment of the document,
The root of the scoping subtree is called the
scoping root
When a selector is
scoped
it matches an element only if the element is a descendant of the
scoping root
(The rest of the selector can match unrestricted;
it’s only the final matched elements that must be within the scope.)
For example,
the
querySelector()
method defined in
[DOM]
allows the author to evaluate a
scoped
selector
relative to the element it’s called on.
A call like
widget
querySelector
"a"
will thus only find
elements inside of the
widget
element,
ignoring any other
s that might be scattered throughout the document.
3.4.
Relative Selectors
Certain contexts may accept
relative selectors
which are a shorthand for selectors that represent elements relative to one or more
relative selector anchor elements
Relative selectors begin with a
combinator
with a selector representing the
anchor element
implied at the start of the selector.
(If no combinator is present,
the
descendant combinator
is implied.)
Relative selectors are represented by
in the selectors
grammar
and lists of them by
3.5.
Pseudo-classes
Pseudo-classes
are
simple selectors
that permit selection based on
information that lies outside of the document tree
or that can be awkward or impossible to express using the other simple selectors.
They can also be dynamic,
in the sense that an element can acquire or lose a pseudo-class
while a user interacts with the document,
without the document itself changing.
Pseudo-classes
do not appear in or modify the document source or document tree.
The syntax of a
pseudo-class
consists of a ":" (U+003A COLON)
followed by the name of the
pseudo-class
as a CSS
identifier
and, in the case of a
functional pseudo-class
a pair of parentheses containing its arguments.
For example,
:valid
is a regular pseudo-class,
and
:lang()
is a
functional pseudo-class
Like all CSS keywords,
pseudo-class
names are
ASCII case-insensitive
No
white space
is allowed between the colon and the name of the
pseudo-class
nor, as usual for CSS syntax,
between a
functional pseudo-class
’s name and its opening parenthesis
(which thus form a CSS
function token
).
Also as usual,
white space
is allowed around the arguments inside the parentheses
of a functional pseudo-class
unless otherwise specified.
Like other
simple selectors
pseudo-classes
are allowed in all
compound selectors
contained in a selector,
and must follow the
type selector
or
universal selector
, if present.
Note:
Some
pseudo-classes
are mutually exclusive
(such that a
compound selector
containing them, while valid, will never match anything),
while others can apply simultaneously to the same element.
3.6.
Pseudo-elements
Tests
x-pseudo-element.html
(live test)
(source)
Similar to how certain
pseudo-classes
represent additional state information
not directly present in the document tree,
pseudo-element
represents an
element
not directly present in the document tree.
They are used to create abstractions about the document tree
beyond those provided by the document tree.
For example,
pseudo-elements can be used to select portions of the document
that do not correspond to a document-language element
(including such ranges as don’t align to element boundaries or fit within its tree structure);
that represent content not in the document tree or in an alternate projection of the document tree;
or that rely on information provided by styling, layout, user interaction, and other processes that are not reflected in the document tree.
For instance, document languages do not offer mechanisms to access
the first letter or first line of an element’s content,
but there exist
pseudo-elements
::first-letter
and
::first-line
that allow those things to be styled.
Notice especially that in the case of
::first-line
which portion of content is represented by the pseudo-element
depends on layout information
that cannot be inferred from the document tree.
Pseudo-elements
can also represent content that doesn’t exist in the source document at all,
such as the
::before
and
::after
pseudo-elements
which allow additional content to be inserted before or after the contents of any element.
Like
pseudo-classes
pseudo-elements
do not appear in or modify the document source or document tree.
Accordingly, they also do not affect the interpretation of
structural pseudo-classes
or other selectors pertaining to their
originating element
or its tree.
The host language defines which pseudo-elements exist, their type, and their abilities.
Pseudo-elements that exist in CSS
are defined in
[CSS21]
(Level 2),
[SELECT]
(Level 3), and
[CSS-PSEUDO-4]
(Level 4).
3.6.1.
Syntax
The syntax of a
pseudo-element
is "::" (two U+003A COLON characters)
followed by the name of the
pseudo-element
as an
identifier
and, in the case of a
functional pseudo-element
a pair of parentheses containing its arguments.
Pseudo-element
names are
ASCII case-insensitive
No
white space
is allowed between the two colons, or between the colons and the name.
Because
CSS Level 1
and
CSS Level 2
conflated pseudo-elements and pseudo-classes by sharing a single-colon syntax for both,
user agents must also accept the previous one-colon notation
for the Level 1 & 2 pseudo-elements
::before
::after
::first-line
, and
::first-letter
).
This compatibility notation is not allowed for any other
pseudo-elements
However, as this syntax is deprecated,
authors should use the Level 3+ double-colon syntax for these
pseudo-elements
Pseudo-elements
are
featureless
and so can’t be matched by any other selector.
3.6.2.
Binding to the Document Tree
Pseudo-elements
do not exist independently in the tree:
they are always bound to another element on the page,
called their
originating element
Syntactically, a
pseudo-element
immediately follows
the
compound selector
representing its
originating element
If this
compound selector
is omitted,
it is assumed to be the
universal selector
For example, in the selector
div a::before
the
elements matched by the selector are the
originating elements
for the
::before
pseudo-elements attached to them.
The selector
::first-line
is equivalent to
*::first-line
which selects the
::first-line
pseudo-element on
every
element in the document.
When a
pseudo-element
is encountered in a selector,
the part of the selector before the
pseudo-element
selects the
originating element
for the
pseudo-element
the part of the selector after it, if any, applies to the
pseudo-element
itself.
(See below.)
3.6.3.
Pseudo-classing Pseudo-elements
Certain
pseudo-elements
may be immediately followed
by any combination of certain
pseudo-classes
in which case the
pseudo-element
is represented only when it is in the corresponding state.
This specification allows any
pseudo-element
to be followed
by any combination of the
logical combination pseudo-classes
and the
user action pseudo-classes
Other specifications may allow additional
pseudo-classes
to be attached to particular
pseudo-elements
Combinations that are not explicitly allowed are
invalid selectors
Note:
The
logical combination pseudo-classes
pass any restrictions on validity of selectors at their position
to their arguments.
For example, since the
:hover
pseudo-class specifies
that it can apply to any pseudo-element,
::first-line:hover
will match when the first line is hovered.
However, since neither
:focus
nor
::first-line
define that
:focus
can apply to
::first-line
the selector
::first-line:focus
will never match anything.
Notice that
::first-line:hover
is very different from
:hover::first-line
which matches the first line of any originating element that is hovered!
For example,
:hover::first-line
also matches the first line of a paragraph
when the second line of the paragraph is hovered,
whereas
::first-line:hover
only matches if the first line itself is hovered.
3.6.4.
Sub-pseudo-elements
Some
pseudo-elements
are able to be the
originating element
of other
pseudo-elements
which are defined as the
sub-pseudo-elements
of this
originating pseudo-element
For example,
when
::before
is given a
list-item
display type
it becomes the
originating pseudo-element
of its
::before::marker
sub-pseudo-element
Where disambiguation is needed,
the term
ultimate originating element
refers to the real (non-pseudo) element
from which a
pseudo-element
originates.
Unless the corresponding
sub-pseudo-element
is explicitly defined to exist in another specification,
pseudo-element selectors are not valid
when compounded to another pseudo-element selector.
So, for example,
::before::before
is an invalid selector,
but
::before::marker
is valid
(in implementations that support the
::before::marker
sub-pseudo-element
).
3.6.5.
Internal Structure
Some
pseudo-elements
are defined to have internal structure.
These
pseudo-elements
may be followed by child/descendant combinators
to express those relationships.
Selectors containing
combinators
after the pseudo-element
are otherwise invalid.
For example,
::first-letter + span
and
::first-letter em
are invalid selectors.
However, if a new
::shadow
pseudo-element were defined to have internal structure,
::shadow > p
would be a valid selector.
Note:
A future specification may expand the capabilities of existing pseudo-elements,
so some of these currently-invalid selectors (e.g.
::first-line :any-link
may become valid in the future.
The children of such
pseudo-elements
can simultaneously be children of other elements, too.
However, at least in CSS, their rendering must be defined so as to maintain the tree-ness of the
box tree
3.7.
Characters and case sensitivity
Tests
case-insensitive-parent.html
(live test)
(source)
quirks-mode-stylesheet-dynamic-add-001.html
(live test)
(source)
selectors-case-sensitive-001.html
(live test)
(source)
All Selectors syntax is
ASCII case-insensitive
(i.e. [a-z] and [A-Z] are equivalent),
except for the parts
that are not under the control of Selectors:
specifically,
the case-sensitivity of
document language element names,
attribute names,
and attribute values
depends on the document language.
For example,
in HTML, element and attribute names are ASCII case-insensitive
but in XML, they are case-sensitive.
Case sensitivity of namespace prefixes is defined in
[CSS3NAMESPACE]
Case sensitivity of
language ranges
is defined in the
:lang()
section.
White space
in Selectors consists of the
code points SPACE (U+0020), TAB (U+0009), LINE FEED (U+000A),
CARRIAGE RETURN (U+000D), and FORM FEED (U+000C).
Other space-like code points, such as EM SPACE (U+2003) and
IDEOGRAPHIC SPACE (U+3000), are never considered syntactic white space.
Code points in Selectors can be escaped with a backslash
according to the same
escaping rules
as CSS.
[CSS21]
Note that escaping a code point “cancels out”
any special meaning it may have in Selectors.
For example, the selector
#foo>a
contains a combinator,
but
#foo\>a
instead selects an element with the id
foo>a
3.8.
Declaring Namespace Prefixes
Certain selectors support namespace prefixes.
The mechanism by which namespace prefixes are
declared
should be specified by the language that uses Selectors.
If the language does not specify a namespace prefix declaration mechanism,
then no prefixes are declared.
In CSS, namespace prefixes are declared with the
@namespace
rule.
[CSS3NAMESPACE]
3.9.
Invalid Selectors and Error Handling
Tests
selectorText-dynamic-001.html
(live test)
(source)
sheet-going-away-001.html
(live test)
(source)
sheet-going-away-002.html
(live test)
(source)
User agents must observe the rules for handling
invalid selectors
a parsing error in a selector,
e.g. an unrecognized token or a token which is not allowed at the current parsing point
(see overall
§ 16 Grammar
and per-selector syntax definitions),
causes that selector to be invalid.
a simple selector containing an
undeclared namespace prefix
is invalid
a selector containing an invalid simple selector, an invalid combinator
or an invalid token is invalid.
a selector list containing an invalid selector is invalid.
an empty selector, i.e. one that contains no
compound selector
, is invalid.
Note:
Consistent with CSS’s forwards-compatible parsing principle,
UAs
must
treat as
invalid
any pseudo-classes, pseudo-elements, combinators, or other syntactic constructs
for which they have no usable level of support.
See
Partial implementations
An
invalid selector
represents, and therefore matches, nothing.
3.10.
Legacy Aliases
Some selectors have a
legacy selector alias
This is a name which, at parse time, is converted to the standard name
(and thus does not appear anywhere in any object model representing the selector).
4.
Logical Combinations
Tests
is-where-pseudo-containing-hard-pseudo-and-never-matching.html
(live test)
(source)
is-where-pseudo-containing-hard-pseudo.html
(live test)
(source)
Selector logic can be manipulated by
compounding
(logical AND),
selector lists
(logical OR),
and the
logical combination pseudo-classes
:is()
:where()
, and
:not()
The
logical combination pseudo-classes
are allowed anywhere that any other
pseudo-classes
are allowed,
but pass any restrictions to their arguments.
(For example, if only
compound selectors
are allowed,
then only
compound selectors
are valid within an
:is()
.)
Note:
Since inside
:is()
and
:where()
invalid arguments are dropped without invaliding the
pseudo-class
itself,
selector arguments that are invalidated by contextual restrictions
likewise do not invalidate the
:is()
pseudo-class itself.
4.1.
Selector Lists
A comma-separated list of selectors represents the union of all
elements selected by each of the individual selectors in the
selector list
(A comma is U+002C.) For example, in CSS when several selectors share
the same declarations, they may be grouped into a comma-separated
list. White space may appear before and/or after the comma.
CSS example:
In this example, we condense three rules with identical
declarations into one. Thus,
h1 { font-family: sans-serif }
h2 { font-family: sans-serif }
h3 { font-family: sans-serif }
is equivalent to:
h1, h2, h3 { font-family: sans-serif }
Warning
: the equivalence is true in this example
because all the selectors are valid selectors. If just one of these
selectors were invalid, the entire
selector list
would be
invalid. This would invalidate the rule for all three heading
elements, whereas in the former case only one of the three individual
heading rules would be invalidated.
Invalid CSS example:
h1 { font-family: sans-serif }
h2..foo { font-family: sans-serif }
h3 { font-family: sans-serif }
is not equivalent to:
h1, h2..foo, h3 { font-family: sans-serif }
because the above selector (
h1, h2..foo, h3
is entirely invalid and the entire style rule is dropped. (When
the selectors are not grouped, only the rule for
h2..foo
is dropped.)
4.2.
The Matches-Any Pseudo-class:
:is()
Tests
is.html
(live test)
(source)
is-default-ns-001.html
(live test)
(source)
is-default-ns-002.html
(live test)
(source)
is-default-ns-003.html
(live test)
(source)
is-default-ns-002.html
(live test)
(source)
is-default-ns-003.html
(live test)
(source)
is-nested.html
(live test)
(source)
is-specificity-shadow.html
(live test)
(source)
is-specificity.html
(live test)
(source)
is-where-basic.html
(live test)
(source)
is-where-error-crash.html
(live test)
(source)
is-where-error-recovery.html
(live test)
(source)
is-where-not.html
(live test)
(source)
is-where-pseudo-classes.html
(live test)
(source)
is-where-pseudo-elements.html
(live test)
(source)
is-where-shadow.html
(live test)
(source)
is-where-visited.html
(live test)
(source)
parse-is-where.html
(live test)
(source)
parse-is.html
(live test)
(source)
query-is.html
(live test)
(source)
The matches-any pseudo-class,
:is()
is a functional pseudo-class taking a
as its sole argument.
If the argument, after parsing, is an empty list,
the pseudo-class is valid but matches nothing.
Otherwise, the pseudo-class matches any element
that matches any of the selectors in the list.
Note:
The specificity of the
:is()
pseudo-class
is replaced by the specificity of its most specific argument.
Thus, a selector written with
:is()
does not necessarily have equivalent specificity
to the equivalent selector written without
:is()
For example, if we have
:is(ul, ol, .list) > [hidden]
and
ul > [hidden], ol > [hidden], .list > [hidden]
[hidden]
child of an
ol
matches the first selector
with a specificity of (0,2,0)
whereas it matches the second selector
with a specificity of (0,1,1).
See
§ 15 Calculating a selector’s specificity
Pseudo-elements cannot be represented by the matches-any pseudo-class;
they are not valid within
:is()
Default namespace declarations do not affect the
compound selector
representing the
subject
of any selector
within a
:is()
pseudo-class,
unless that compound selector contains
an explicit
universal selector
or
type selector
For example, the following selector matches any element that is being
hovered or focused, regardless of its namespace. In particular, it
is not limited to only matching elements in the default namespace
that are being hovered or focused.
*|*:is(:hover, :focus)
The following selector, however, represents only hovered or focused
elements that are in the default namespace, because it uses an explicit
universal selector within the
:is()
notation:
*|*:is(*:hover, *:focus)
As previous drafts of this specification
used the name
:matches()
for this pseudo-class,
UAs may additionally implement this obsolete name
as a
legacy selector alias
for
:is()
if needed for backwards-compatibility.
4.3.
The Negation (Matches-None) Pseudo-class:
:not()
Tests
not-001.html
(live test)
(source)
not-002.html
(live test)
(source)
not-complex.html
(live test)
(source)
not-default-ns-001.html
(live test)
(source)
not-default-ns-002.html
(live test)
(source)
not-default-ns-003.html
(live test)
(source)
not-links.html
(live test)
(source)
not-specificity.html
(live test)
(source)
parse-not.html
(live test)
(source)
query-where.html
(live test)
(source)
The negation pseudo-class,
:not()
is a functional pseudo-class taking a
as an argument.
It represents an element that is not represented by its argument.
Note:
In Selectors Level 3,
only a single
simple selector
was allowed as the argument to
:not()
Note:
The specificity of the
:not()
pseudo-class
is replaced by the specificity of the most specific selector in its argument;
thus it has the exact behavior of
:not(:is(
argument
))
See
§ 15 Calculating a selector’s specificity
Pseudo-elements cannot be represented by the negation pseudo-class;
they are not valid within
:not()
For example, the following selector matches all
button
elements in an HTML document
that are not disabled.
button:not([DISABLED])
The following selector represents all but FOO elements.
*:not(FOO)
The following compound selector represents all HTML elements
except links.
html|*:not(:link):not(:visited)
As with
:is()
default namespace declarations do not affect the
compound selector
representing the
subject
of any selector
within a
:not()
pseudo-class,
unless that compound selector contains
an explicit
universal selector
or
type selector
(See
:is()
for examples.)
Note:
The
:not()
pseudo-class allows useless selectors to be written.
For instance
:not(*|*)
, which represents no element at all,
or
div:not(span)
, which is equivalent to
div
but with a higher specificity.
4.4.
The Specificity-adjustment Pseudo-class:
:where()
Tests
where.html
(live test)
(source)
parse-where.html
(live test)
(source)
pseudo-where-crash.html
(live test)
(source)
The Specificity-adjustment pseudo-class,
:where()
is a functional pseudo-class
with the same syntax and functionality as
:is()
Unlike
:is()
, neither the
:where()
pseudo-class, nor any of its arguments,
contribute to the
specificity
of the selector—its
specificity
is always zero.
This is useful for introducing filters in a selector
while keeping the associated style declarations easy to override.
Below is a common example where the specificity heuristic fails
to match author expectations:
a:not(:hover) {
text-decoration: none;
nav a {
/* Has no effect */
text-decoration: underline;
However, by using
:where()
the author can explicitly declare their intent:
a:where(:not(:hover)) {
text-decoration: none;
nav a {
/* Works now! */
text-decoration: underline;
Note:
Future levels of Selectors may introduce an additional argument
to explicitly set the specificity of that instance of the pseudo-class.
4.5.
The Relational Pseudo-class:
:has()
Tests
has-argument-with-explicit-scope.html
(live test)
(source)
has-basic.html
(live test)
(source)
has-display-none-checked.html
(live test)
(source)
has-focus-display-change.html
(live test)
(source)
has-matches-to-uninserted-elements.html
(live test)
(source)
has-nth-of-crash.html
(live test)
(source)
has-relative-argument.html
(live test)
(source)
has-sibling-chrome-crash.html
(live test)
(source)
has-specificity.html
(live test)
(source)
has-style-sharing-001.html
(live test)
(source)
has-style-sharing-002.html
(live test)
(source)
has-style-sharing-003.html
(live test)
(source)
has-style-sharing-004.html
(live test)
(source)
has-style-sharing-005.html
(live test)
(source)
has-style-sharing-006.html
(live test)
(source)
has-style-sharing-007.html
(live test)
(source)
has-style-sharing-pseudo-001.html
(live test)
(source)
has-style-sharing-pseudo-002.html
(live test)
(source)
has-style-sharing-pseudo-003.html
(live test)
(source)
has-style-sharing-pseudo-004.html
(live test)
(source)
has-style-sharing-pseudo-005.html
(live test)
(source)
has-style-sharing-pseudo-006.html
(live test)
(source)
has-style-sharing-pseudo-007.html
(live test)
(source)
has-style-sharing-pseudo-008.html
(live test)
(source)
has-visited.html
(live test)
(source)
attribute-or-elemental-selectors-in-has.html
(live test)
(source)
child-indexed-pseudo-classes-in-has.html
(live test)
(source)
has-pseudoclass-only-crash.html
(live test)
(source)
defined-in-has.html
(live test)
(source)
dir-pseudo-class-in-has.html
(live test)
(source)
empty-pseudo-in-has.html
(live test)
(source)
fullscreen-pseudo-class-in-has.html
(live test)
(source)
has-append-first-node.html
(live test)
(source)
has-complexity.html
(live test)
(source)
has-css-nesting-shared.html
(live test)
(source)
has-in-adjacent-position.html
(live test)
(source)
has-in-ancestor-position.html
(live test)
(source)
has-in-parent-position.html
(live test)
(source)
has-in-sibling-position.html
(live test)
(source)
has-invalidation-after-removing-non-first-element.html
(live test)
(source)
has-invalidation-first-in-sibling-chain.html
(live test)
(source)
has-invalidation-for-wiping-an-element.html
(live test)
(source)
has-nested-pseudo-001-crash.html
(live test)
(source)
has-nested-pseudo-002-crash.html
(live test)
(source)
has-nested-pseudo-003-crash.html
(live test)
(source)
has-pseudo-element.html
(live test)
(source)
has-pseudoclass-only.html
(live test)
(source)
has-sibling-insertion-removal.html
(live test)
(source)
has-sibling.html
(live test)
(source)
has-side-effect.html
(live test)
(source)
has-unstyled.html
(live test)
(source)
has-with-is-child-combinator.html
(live test)
(source)
has-with-nesting-parent-containing-complex.html
(live test)
(source)
has-with-nesting-parent-containing-hover.html
(live test)
(source)
has-with-not.html
(live test)
(source)
has-with-nth-child-sibling-remove.html
(live test)
(source)
has-with-nth-child.html
(live test)
(source)
has-with-pseudo-class.html
(live test)
(source)
host-context-pseudo-class-in-has.html
(live test)
(source)
host-has-shadow-tree-element-at-nonsubject-position.html
(live test)
(source)
host-has-shadow-tree-element-at-subject-position.html
(live test)
(source)
host-pseudo-class-in-has.html
(live test)
(source)
input-pseudo-classes-in-has.html
(live test)
(source)
is-pseudo-containing-complex-in-has.html
(live test)
(source)
is-pseudo-containing-sibling-relationship-in-has.html
(live test)
(source)
lang-pseudo-class-in-has-document-element.html
(live test)
(source)
lang-pseudo-class-in-has-multiple-document-elements.html
(live test)
(source)
lang-pseudo-class-in-has-xhtml.xhtml
(live test)
(source)
lang-pseudo-class-in-has.html
(live test)
(source)
link-pseudo-class-in-has.html
(live test)
(source)
link-pseudo-in-has.html
(live test)
(source)
location-pseudo-classes-in-has.html
(live test)
(source)
media-loading-pseudo-classes-in-has.html
(live test)
(source)
media-pseudo-classes-in-has.html
(live test)
(source)
modal-pseudo-class-in-has.html
(live test)
(source)
negated-has-in-nonsubject-position.html
(live test)
(source)
not-pseudo-containing-complex-in-has.html
(live test)
(source)
not-pseudo-containing-sibling-relationship-in-has.html
(live test)
(source)
state-in-has.html
(live test)
(source)
subject-has-invalidation-with-display-none-anchor-element.html
(live test)
(source)
target-pseudo-in-has.html
(live test)
(source)
typed-child-indexed-pseudo-classes-in-has.html
(live test)
(source)
user-action-pseudo-classes-in-has.html
(live test)
(source)
parse-has-disallow-nesting-has-inside-has.html
(live test)
(source)
parse-has-forgiving-selector.html
(live test)
(source)
parse-has.html
(live test)
(source)
The relational pseudo-class,
:has()
is a functional pseudo-class taking a
as an argument.
It represents an element if any of the
relative selectors
would match at least one element
when
anchored against
this element.
The
:has()
pseudo-class cannot be nested;
:has()
is not valid within
:has()
Also, unless explicitly defined as a
:has-allowed pseudo-element
pseudo-elements
are not valid selectors within
:has()
(This specification does not define any
:has-allowed pseudo-elements
but other specifications may do so.)
Note:
Pseudo-elements are generally excluded from
:has()
because
many of them exist conditionally, based on the styling of their ancestors,
so allowing these to be queried by
:has()
would introduce cycles.
Note:
Since
:has()
takes a
its arguments are
inherently
complex selectors
(because they start, perhaps implicitly, with a combinator).
This means
:has()
cannot be used in contexts that don’t allow complex selectors;
its arguments will be guaranteed to be invalid.
For example, the following selector matches only
elements that contain an
child:
a:has(> img)
The following selector matches a
element
immediately followed by another
element:
dt:has(+ dt)
The following selector matches
elements
that don’t contain any heading elements:
section:not(:has(h1, h2, h3, h4, h5, h6))
Note that ordering matters in the above selector.
Swapping the nesting of the two pseudo-classes, like:
section:has(:not(h1, h2, h3, h4, h5, h6))
...would result in matching any
element
which contains anything that’s not a heading element.
5.
Elemental selectors
5.1.
Type (tag name) selector
type selector
is the name of a document language element type,
and represents an instance of that element type in the document tree.
For example, the selector
h1
represents an
h1
element in the document.
type selector
is written as a
CSS qualified name
an
identifier
with an optional namespace prefix.
[CSS3NAMESPACE]
(See
§ 5.3 Namespaces in Elemental Selectors
.)
5.2.
Universal selector
Tests
parse-universal.html
(live test)
(source)
The
universal selector
is a special
type selector
that represents an element of any element type.
It is written as a
CSS qualified name
with an asterisk (
U+002A) as the local name.
Like a
type selector
the
universal selector
can be qualified by a namespace,
restricting it to only elements belonging to that namespace,
and is affected by a default namespace as defined in
§ 5.3 Namespaces in Elemental Selectors
Unless an element is
featureless
the presence of a
universal selector
has no effect on whether the element matches the selector.
Featureless
elements do not match any selector,
including the
universal selector
.)
*[hreflang|=en]
and
[hreflang|=en]
are equivalent,
*.warning
and
.warning
are equivalent,
*#myid
and
#myid
are equivalent.
The
universal selector
follows the same syntax rules as other
type selectors
only one can appear per
compound selector
and it must be the first
simple selector
in the
compound selector
Note:
In some cases, adding a
universal selector
can make a selector easier to read,
even though it has no effect on the matching behavior.
For example,
div :first-child
and
div:first-child
are somewhat difficult to tell apart at a quick glance,
but writing the former as
div *:first-child
makes the difference obvious.
5.3.
Namespaces in Elemental Selectors
Type selectors
and
universal selectors
allow an optional namespace component:
a namespace prefix that has been previously
declared
may be prepended to the element name separated by the namespace separator “vertical bar” (
U+007C).
(See, e.g.,
[XML-NAMES]
for the use of namespaces in XML.)
It has the following meaning in each form:
ns|E
elements with name E in namespace ns
*|E
elements with name E in any namespace,
including those without a namespace
|E
elements with name E without a namespace
if no default namespace has been
declared
for selectors,
this is equivalent to *|E.
Otherwise it is equivalent to ns|E
where ns is the default namespace.
CSS examples:
@namespace foo url(http://www.example.com);
foo|h1 { color: blue } /* first rule */
foo|* { color: yellow } /* second rule */
|h1 { color: red } /* ...*/
*|h1 { color: green }
h1 { color: green }
The first rule (not counting the
@namespace
at-rule)
will match only
h1
elements in the
"http://www.example.com" namespace.
The second rule will match all elements in the
"http://www.example.com" namespace.
The third rule will match only
h1
elements with
no namespace.
The fourth rule will match
h1
elements in any
namespace (including those without any namespace).
The last rule is equivalent to the fourth rule because no default
namespace has been defined.
If a
default namespace
is declared,
compound selectors
without
type selectors
in them
still only match elements in that default namespace.
For example,
in the following style sheet:
@namespace url("http://example.com/foo");
.special { ... } Je suis français.
The
.special
selector only matches elements in the "http://example.com/foo" namespace,
even though no reference to the type name (which is paired with the namespace in the DOM) appeared.
type selector
or
universal selector
containing a namespace prefix
that has not been previously
declared
is an
invalid selector
5.4.
The Defined Pseudo-class:
:defined
Tests
defined.html
(live test)
(source)
In some host languages,
elements can have a distinction between being “defined”/“constructed” or not.
The
:defined
pseudo-class
matches elements
that are fully defined,
as dictated by the host language.
If the host language does not have this sort of distinction,
all elements in it match
:defined
In HTML, all built-in elements are always considered to be defined,
so the following example will always match:
defined
...
Custom elements
, on the other hand,
start out
un
defined,
and only become defined when
properly registered
This means the
:defined
pseudo-class
can be used to hide a custom element
until it has been registered:
custom-element { visibility: hidden }
custom-element:defined { visibility: visible }
6.
Attribute selectors
Tests
style-attribute-selector.html
(live test)
(source)
attribute.html
(live test)
(source)
class-id-attr.html
(live test)
(source)
missing-right-token.html
(live test)
(source)
parse-attribute.html
(live test)
(source)
selectors-attr-many.html
(live test)
(source)
Selectors allow the representation of an element’s attributes. When
a selector is used as an expression to match against an element,
an
attribute selector
must be considered to match an element if that
element has an attribute that matches the attribute represented by the
attribute selector.
Add comma-separated syntax for
multiple-value matching
e.g. [rel ~= next, prev, up, first, last]
6.1.
Attribute presence and value selectors
CSS2 introduced four attribute selectors:
[att]
Represents an element with the
att
attribute,
whatever the value of the attribute.
[att=val]
Represents an element with the
att
attribute
whose value is exactly "val".
[att~=val]
Represents an element with the
att
attribute
whose value is a
whitespace
-separated list of words,
one of which is exactly "val".
If "val" contains whitespace,
it will never represent anything
(since the words are
separated
by spaces).
Also if "val" is the empty string,
it will never represent anything.
[att|=val]
Represents an element with the
att
attribute,
its value either being exactly "val"
or beginning with "val" immediately followed by "-" (U+002D).
This is primarily intended to allow language subcode matches
(e.g., the
hreflang
attribute on the
element in HTML)
as described in BCP 47 (
[BCP47]
) or its successor.
For
lang
(or
xml:lang
) language subcode matching,
please see the
:lang()
pseudo-class.
Attribute values must be
s or
s.
[CSS3SYN]
Examples:
The following attribute selector represents an
h1
element
that carries the
title
attribute,
whatever its value:
h1[title]
In the following example, the selector represents a
span
element whose
class
attribute has
exactly the value "example":
span[class="example"]
Multiple attribute selectors can be used to represent several
attributes of an element, or several conditions on the same
attribute. Here, the selector represents a
span
element
whose
hello
attribute has exactly the value "Cleveland"
and whose
goodbye
attribute has exactly the value
"Columbus":
span[hello="Cleveland"][goodbye="Columbus"]
The following CSS rules illustrate the differences between
"=" and "~=". The first selector would match, for example, an
element with the value "copyright copyleft
copyeditor" on a
rel
attribute. The second selector
would only match an
element with an
href
attribute having the exact value "http://www.w3.org/".
a[rel~="copyright"] { ... }
a[href="http://www.w3.org/"] { ... }
The following selector represents an
element
whose
hreflang
attribute is exactly "fr".
a[hreflang=fr]
The following selector represents an
element for
which the value of the
hreflang
attribute begins with
"en", including "en", "en-US", and "en-scouse":
a[hreflang|="en"]
The following selectors represent a
DIALOGUE
element
whenever it has one of two different values for an attribute
character
DIALOGUE[character=romeo]
DIALOGUE[character=juliet]
6.2.
Substring matching attribute selectors
Three additional attribute selectors are provided for matching
substrings in the value of an attribute:
[att^=val]
Represents an element with the
att
attribute
whose value begins with the prefix "val".
If "val" is the empty string
then the selector does not represent anything.
[att$=val]
Represents an element with the
att
attribute
whose value ends with the suffix "val".
If "val" is the empty string
then the selector does not represent anything.
[att*=val]
Represents an element with the
att
attribute
whose value contains at least one instance of the substring "val".
If "val" is the empty string
then the selector does not represent anything.
Attribute values must be
s or
s.
Examples:
The following selector represents an HTML
object
element,
referencing an image:
object[type^="image/"]
The following selector represents an HTML
element
with an
href
attribute whose value ends with ".html".
a[href$=".html"]
The following selector represents an HTML paragraph
with a
title
attribute whose value contains the substring "hello"
p[title*="hello"]
6.3.
Case-sensitivity
Tests
cssom.html
(live test)
(source)
semantics.html
(live test)
(source)
syntax.html
(live test)
(source)
By default case-sensitivity of attribute names and values in selectors
depends on the document language.
To match attribute values
ASCII case-insensitively
regardless of document language rules,
the attribute selector may include the identifier
before the closing bracket (
).
When this flag is present,
UAs must match the attribute’s value
ASCII case-insensitively
(i.e. [a-z] and [A-Z] are considered equivalent).
Alternately, the attribute selector may include the identifier
before the closing bracket (
);
in this case the UA must match the value case-sensitively,
with “
identical to
” semantics
[INFRA]
regardless of document language rules.
Like the rest of Selectors syntax,
the
and
identifiers themselves
are
ASCII case-insensitive
The following rule will style the
frame
attribute when it
has a value of
hsides
, whether that value is represented
as
hsides
HSIDES
hSides
, etc.
even in an XML environment where attribute values are case-sensitive.
[frame=hsides i] { border-style: solid none; }
The following rule will style lists with
type="a"
attributes differently than
type="A"
even though HTML defines the
type
attribute
to be case-insensitive.
[type="a" s] { list-style: lower-alpha; }
[type="A" s] { list-style: upper-alpha; }
Note:
Some document models normalize case-insensitive attribute values at parse time
such that checking if a string is case-sensitive matching is impossible.
Case-sensitive matching via
flags is only possible
in systems that preserve the original case.
6.4.
Attribute selectors and namespaces
Tests
selectors-namespace-001.xml
(live test)
(source)
The attribute name in an attribute selector is given as a
CSS qualified name
: a namespace prefix that has been previously
declared
may be prepended to the attribute name separated by the namespace
separator "vertical bar" (
). In keeping with
the Namespaces in the XML recommendation, default namespaces do not
apply to attributes, therefore attribute selectors without a namespace
component apply only to attributes that have no namespace (equivalent
to
|attr
). An asterisk may be used for
the namespace prefix indicating that the selector is to match all
attribute names without regard to the attribute’s namespace.
An attribute selector with an attribute name containing a namespace
prefix that has not been previously
declared
is
an invalid selector.
CSS examples:
@namespace foo "http://www.example.com";
[foo|att=val] { color: blue }
[*|att] { color: yellow }
[|att] { color: green }
[att] { color: green }
The first rule will match only elements with the attribute
att
in the "http://www.example.com" namespace with the
value "val".
The second rule will match only elements with the attribute
att
regardless of the namespace of the attribute
(including no namespace).
The last two rules are equivalent and will match only elements
with the attribute
att
where the attribute is not
in a namespace.
6.5.
Default attribute values in DTDs
Attribute selectors represent attribute values in the document tree.
How that document tree is constructed is outside the scope of Selectors.
In some document formats default attribute values can be defined in a DTD or
elsewhere, but these can only be selected by attribute selectors if they
appear in the document tree. Selectors should be designed so that they
work whether or not the default values are included in the document tree.
For example, a XML UA may, but is
not
required to,
read an “external subset” of the DTD, but
is
required to
look for default attribute values in the document’s “internal subset”.
(See, e.g.,
[XML10]
for definitions of these subsets.)
Depending on the UA, a default attribute value defined in the external subset of the DTD
might or might not appear in the document tree.
A UA that recognizes an XML namespace may, but is not required to use its
knowledge of that namespace to treat default attribute values as if
they were present in the document. (For example, an XHTML UA is not
required to use its built-in knowledge of the XHTML DTD. See, e.g.,
[XML-NAMES]
for details on namespaces in XML
1.0.)
Note:
Typically, implementations
choose to ignore external subsets. This corresponds to the behavior
of non-validating processors as defined by the XML specification.
Example:
Consider an element
EXAMPLE
with an attribute
radix
that has a default value of
"decimal"
. The DTD fragment might be
If the style sheet contains the rules
EXAMPLE[radix=decimal] { /*... default property settings ...*/ }
EXAMPLE[radix=octal] { /*... other settings...*/ }
the first rule might not match elements whose
radix
attribute is
set by default, i.e. not set explicitly. To catch all cases, the
attribute selector for the default value must be dropped:
EXAMPLE { /*... default property settings ...*/ }
EXAMPLE[radix=octal] { /*... other settings...*/ }
Here, because the selector
EXAMPLE[radix=octal]
is
more specific than the type selector alone, the style declarations in
the second rule will override those in the first for elements that
have a
radix
attribute value of
"octal"
. Care has to be taken that
all property declarations that are to apply only to the default case
are overridden in the non-default cases' style rules.
6.6.
Class selectors
Tests
parse-class.html
(live test)
(source)
xml-class-selector.xml
(live test)
(source)
The
class selector
is given as a full stop (. U+002E) immediately
followed by an identifier. It represents an element belonging to the
class identified by the identifier, as defined by the document language.
For example, in
[HTML5]
[SVG11]
, and
[MATHML]
membership in a
class is given by the
class
attribute: in these languages
it is equivalent to the
~=
notation applied to the
local
class
attribute
(i.e.
[class~=
identifier
).
CSS examples:
We can assign style information to all elements with
class~="pastoral"
as follows:
*.pastoral { color: green } /* all elements with class~=pastoral */
or just
.pastoral { color: green } /* all elements with class~=pastoral */
The following assigns style only to H1 elements with
class~="pastoral"
H1.pastoral { color: green } /* H1 elements with class~=pastoral */
Given these rules, the first
H1
instance below would not have
green text, while the second would:Not green
Very green
The following rule matches any
element whose
class
attribute has been assigned a list of
whitespace
-separated values that includes both
pastoral
and
marine
p.pastoral.marine { color: green }
This rule matches when
class="pastoral blue aqua
marine"
but does not match for
class="pastoral
blue"
Note:
Because CSS gives considerable
power to the "class" attribute, authors could conceivably design their
own "document language" based on elements with almost no associated
presentation (such as
div
and
span
in HTML)
and assigning style
information through the "class" attribute. Authors should avoid this
practice since the structural elements of a document language often
have recognized and accepted meanings and author-defined classes may
not.
Note:
If an element has multiple
class attributes, their values must be concatenated with spaces
between the values before searching for the class. As of this time the
working group is not aware of any manner in which this situation can
be reached, however, so this behavior is explicitly non-normative in
this specification.
When matching against a document which is in
quirks mode
class names must be matched
ASCII case-insensitively
class selectors are otherwise case-sensitive,
only matching class names they are
identical to
[INFRA]
6.7.
ID selectors
Tests
historical-xmlid.xht
(live test)
(source)
parse-id.html
(live test)
(source)
Document languages may contain attributes that are declared to be of type ID.
What makes attributes of type ID special
is that no two such attributes can have the same value in a conformant document,
regardless of the type of the elements that carry them;
whatever the document language,
an ID typed attribute can be used to uniquely identify its element.
In HTML all ID attributes are named
id
XML applications may name ID attributes differently,
but the same restriction applies.
Which attribute on an element is considered the “ID attribute” is defined by the document language.
An
ID selector
consists of a “number sign” (U+0023,
immediately followed by the ID value,
which must be a CSS
identifier
An ID selector represents an element instance that has an identifier that matches the identifier in the ID selector.
(It is possible in non-conforming documents for multiple elements to match a single ID selector.)
Examples:
The following ID selector represents an
h1
element
whose ID-typed attribute has the value "chapter1":
h1#chapter1
The following ID selector represents any element whose ID-typed
attribute has the value "chapter1":
#chapter1
The following selector represents any element whose ID-typed
attribute has the value "z98y".
*#z98y
Note:
In XML 1.0
[XML10]
, the information about which attribute
contains an element’s IDs is contained in a DTD or a schema. When
parsing XML, UAs do not always read the DTD, and thus may not know
what the ID of an element is (though a UA may have namespace-specific
knowledge that allows it to determine which attribute is the ID
attribute for that namespace). If a style sheet author knows or
suspects that a UA may not know what the ID of an element is, they
should use normal attribute selectors instead:
[name=p371]
instead of
#p371
If an element has multiple ID attributes, all of them must be
treated as IDs for that element for the purposes of the ID
selector. Such a situation could be reached using mixtures of xml:id,
DOM3 Core, XML DTDs, and namespace-specific knowledge.
When matching against a document which is in
quirks mode
IDs must be matched
ASCII case-insensitively
ID selectors are otherwise case-sensitive,
only matching IDs they are
identical to
[INFRA]
7.
Linguistic Pseudo-classes
7.1.
The Directionality Pseudo-class:
:dir()
Tests
dir-pseudo-in-has.html
(live test)
(source)
dir-pseudo-on-bdi-element.html
(live test)
(source)
dir-pseudo-on-input-element.html
(live test)
(source)
dir-pseudo-update-document-element.html
(live test)
(source)
dir-selector-auto-direction-change-001.html
(live test)
(source)
dir-selector-auto.html
(live test)
(source)
dir-selector-change-001.html
(live test)
(source)
dir-selector-change-002.html
(live test)
(source)
dir-selector-change-003.html
(live test)
(source)
dir-selector-change-004.html
(live test)
(source)
dir-selector-ltr-001.html
(live test)
(source)
dir-selector-ltr-002.html
(live test)
(source)
dir-selector-ltr-003.html
(live test)
(source)
dir-selector-querySelector.html
(live test)
(source)
dir-selector-rtl-001.html
(live test)
(source)
dir-selector-white-space-001.html
(live test)
(source)
dir-style-01a.html
(live test)
(source)
dir-style-01b.html
(live test)
(source)
dir-style-02a.html
(live test)
(source)
dir-style-02b.html
(live test)
(source)
dir-style-03a.html
(live test)
(source)
dir-style-03b.html
(live test)
(source)
dir-style-04.html
(live test)
(source)
part-dir.html
(live test)
(source)
The
:dir()
pseudo-class allows the author to write
selectors that represent an element based on its directionality
as determined by the
document language
For example,
[HTML5]
defines
how to determine the directionality of an element
based on a combination of the
dir
attribute, the surrounding text, and other factors.
As another example, the
its:dir
and
dirRule
element
of the Internationalization Tag Set
[ITS20]
are able to define the directionality of an element in
[XML10]
The
:dir()
pseudo-class does not select based on stylistic
states—for example, the CSS
direction
property does not affect
whether it matches.
The pseudo-class
:dir(ltr)
represents an element that
has a directionality of left-to-right (
ltr
). The
pseudo-class
:dir(rtl)
represents an element that has
a directionality of right-to-left (
rtl
). The argument to
:dir()
must be a single identifier, otherwise the selector
is invalid. White space is optionally allowed between the identifier
and the parentheses. Values other than
ltr
and
rtl
are not invalid, but do not match anything. (If a
future markup spec defines other directionalities, then Selectors may
be extended to allow corresponding values.)
The difference between
:dir(C)
and
[dir=C]
is that
[dir=C]
only performs a comparison against a given
attribute on the element, while the
:dir(C)
pseudo-class
uses the UAs knowledge of the document’s semantics to perform the
comparison. For example, in HTML, the directionality of an element
inherits so that a child without a
dir
attribute will have
the same directionality as its closest ancestor with a valid
dir
attribute. As another example, in HTML,
an element that matches
[dir=auto]
will match either
:dir(ltr)
or
:dir(rtl)
depending on the resolved
directionality of the elements as determined by its contents.
[HTML5]
7.2.
The Language Pseudo-class:
:lang()
Tests
css3-selectors-lang-001.html
(live test)
(source)
css3-selectors-lang-002.html
(live test)
(source)
css3-selectors-lang-004.html
(live test)
(source)
css3-selectors-lang-005.html
(live test)
(source)
css3-selectors-lang-006.html
(live test)
(source)
css3-selectors-lang-007.html
(live test)
(source)
css3-selectors-lang-008.html
(live test)
(source)
css3-selectors-lang-009.html
(live test)
(source)
css3-selectors-lang-010.html
(live test)
(source)
css3-selectors-lang-011.html
(live test)
(source)
css3-selectors-lang-012.html
(live test)
(source)
css3-selectors-lang-014.html
(live test)
(source)
css3-selectors-lang-015.html
(live test)
(source)
css3-selectors-lang-016.html
(live test)
(source)
css3-selectors-lang-021.html
(live test)
(source)
css3-selectors-lang-022.html
(live test)
(source)
css3-selectors-lang-024.html
(live test)
(source)
css3-selectors-lang-025.html
(live test)
(source)
css3-selectors-lang-026.html
(live test)
(source)
css3-selectors-lang-027.html
(live test)
(source)
css3-selectors-lang-028.html
(live test)
(source)
css3-selectors-lang-029.html
(live test)
(source)
css3-selectors-lang-030.html
(live test)
(source)
css3-selectors-lang-031.html
(live test)
(source)
css3-selectors-lang-032.html
(live test)
(source)
css3-selectors-lang-034.html
(live test)
(source)
css3-selectors-lang-035.html
(live test)
(source)
css3-selectors-lang-036.html
(live test)
(source)
css3-selectors-lang-041.html
(live test)
(source)
css3-selectors-lang-042.html
(live test)
(source)
css3-selectors-lang-044.html
(live test)
(source)
css3-selectors-lang-045.html
(live test)
(source)
css3-selectors-lang-046.html
(live test)
(source)
css3-selectors-lang-047.html
(live test)
(source)
css3-selectors-lang-048.html
(live test)
(source)
css3-selectors-lang-049.html
(live test)
(source)
css3-selectors-lang-050.html
(live test)
(source)
css3-selectors-lang-051.html
(live test)
(source)
css3-selectors-lang-052.html
(live test)
(source)
css3-selectors-lang-054.html
(live test)
(source)
css3-selectors-lang-055.html
(live test)
(source)
css3-selectors-lang-056.html
(live test)
(source)
lang-pseudo-class-across-shadow-boundaries.html
(live test)
(source)
lang-pseudo-class-disconnected.html
(live test)
(source)
lang-pseudo-class-empty-attribute.xhtml
(live test)
(source)
part-lang.html
(live test)
(source)
lang-000.html
(live test)
(source)
lang-001.html
(live test)
(source)
lang-002.html
(live test)
(source)
lang-003.html
(live test)
(source)
lang-004.html
(live test)
(source)
lang-005.html
(live test)
(source)
lang-006.html
(live test)
(source)
lang-007.html
(live test)
(source)
lang-008.html
(live test)
(source)
lang-009.html
(live test)
(source)
lang-010.html
(live test)
(source)
lang-011.html
(live test)
(source)
lang-012.html
(live test)
(source)
lang-013.html
(live test)
(source)
lang-014.html
(live test)
(source)
lang-015.html
(live test)
(source)
lang-016.html
(live test)
(source)
lang-017.html
(live test)
(source)
lang-018.html
(live test)
(source)
lang-019.html
(live test)
(source)
lang-020.html
(live test)
(source)
lang-021.html
(live test)
(source)
lang-022.html
(live test)
(source)
lang-023.html
(live test)
(source)
lang-024.html
(live test)
(source)
lang-025.html
(live test)
(source)
If the document language specifies how
the (human)
content language
of an element is determined,
it is possible to write selectors that
represent an element based on its
content language
The
:lang()
pseudo-class,
which accepts a comma-separated list of one or more
language ranges
represents an element whose
content language
is one of the languages listed in its argument.
Each
language range
in
:lang()
must be a valid CSS
or
(Thus language ranges containing asterisks, for example,
must be either correctly escaped or quoted as strings,
e.g.
:lang(\*-Latn)
or
:lang("*-Latn")
.)
Note:
The
content language
of an element is defined by the document language.
For example, in HTML
[HTML5]
, the
content language
is determined
by a combination of the
lang
attribute,
information from
meta
elements,
and possibly also the protocol (e.g. from HTTP headers).
XML languages can use the
xml:lang
attribute
to indicate language information for an element.
[XML10]
The element’s
content language
matches a
language range
if
its
content language
, as represented in BCP 47 syntax,
matches the given
language range
in an
extended filtering
operation per
[RFC4647]
Matching of Language Tags
(section 3.3.2).
Both the
content language
and the
language range
must be
canonicalized
and converted to
extlang form
as per section 4.5 of
[RFC5646]
prior to the
extended filtering
operation.
The matching is performed case-insensitively within the ASCII range.
The
language range
does not need to be a valid language code to
perform this comparison.
For this purpose, a wildcard
language range
"*"
does not match elements whose language is not tagged (e.g.
lang=""
),
but does match elements whose language is tagged as undetermined (
lang=und
).
language range
consisting of an empty string
:lang("")
matches (only) elements whose language is not tagged.
Note:
It is recommended that documents and protocols
indicate language using codes from
[BCP47]
or its successor,
and in the case of XML-based formats, by means of
xml:lang
attributes.
[XML10]
See
“FAQ: Two-letter or three-letter language codes.”
Examples:
The two following selectors represent an HTML document that is in
Belgian French or German. The two next selectors represent
quotations in an arbitrary element in Belgian French
or German.
html:lang(fr-be)
html:lang(de)
:lang(fr-be) > q
:lang(de) > q
Note:
One difference between
:lang(C)
and the
|=
operator
is that the
|=
operator only performs a comparison against a given
attribute on the element, while the
:lang(C)
pseudo-class
uses the UAs knowledge of the document’s semantics to perform the
comparison.
In this HTML example, only the BODY matches
[lang|=fr]
(because it has a LANG attribute) but both
the BODY and the P match
:lang(fr)
(because both are in
French). The P does not match the
[lang|=fr]
because it
does not have a LANG attribute.
Another difference between
:lang(C)
and the
|=
operator
is that
:lang(C)
performs implicit wildcard matching.
For example,
:lang(de-DE)
will match all of
de-DE
de-DE-1996
de-Latn-DE
de-Latf-DE
de-Latn-DE-1996
whereas of those
[lang|=de-DE]
will only match
de-DE
and
de-DE-1996
To perform wildcard matching on the first subtag (the primary language),
an asterisk must be used:
*-CH
will match all of
de-CH
it-CH
fr-CH
, and
rm-CH
To select against an element’s lang attribute value
using this type of language range match,
use both the attribute selector and language pseudo-class together,
e.g.
[lang]:lang(de-DE)
Note:
Wildcard language matching and comma-separated lists are new in Level 4.
8.
Location Pseudo-classes
8.1.
The Hyperlink Pseudo-class:
:any-link
Tests
any-link-attribute-removal.html
(live test)
(source)
any-link-pseudo.html
(live test)
(source)
The
:any-link
pseudo-class represents an element
that acts as the source anchor of a hyperlink.
For example, in
[HTML5]
any
or
area
elements with an
href
attribute are hyperlinks,
and thus match
:any-link
It matches an element if the element would match either
:link
or
:visited
and is equivalent to
:is(:link, :visited)
8.2.
The Link History Pseudo-classes:
:link
and
:visited
Tests
caret-color-visited-inheritance.html
(live test)
(source)
text-emphasis-visited-inheritance.html
(live test)
(source)
text-fill-color-visited-inheritance.html
(live test)
(source)
text-stroke-color-visited-inheritance.html
(live test)
(source)
visited-in-visited-compound.html
(live test)
(source)
visited-inheritance.html
(live test)
(source)
visited-nested.html
(live test)
(source)
visited-part-crash.html
(live test)
(source)
User agents commonly display unvisited
hyperlinks
differently from previously visited ones.
Selectors provides the pseudo-classes
:link
and
:visited
to distinguish them:
The
:link
pseudo-class applies to links that have
not yet been visited.
The
:visited
pseudo-class applies once the link has
been visited by the user.
The two states are mutually exclusive.
After some amount of time,
user agents may choose to return a visited link
to the (unvisited)
:link
state.
The
:visited
pseudo-class comes with obvious privacy implications—letting random websites know what
other
websites you’ve visited
can be problematic for a number of reasons—and so user agents
must
preserve user privacy
in their implementation of
:visited
This specification intentionally does not specify
exactly how to preserve user privacy in this regard,
to allow for user agents to innovate in this space.
The following methods are suggested, however:
Have
:visited
never match,
so all links match
:link
instead.
Carefully track what history entries
could have been observed by a given origin on their own,
and only have links match
:visited
if that visit would have been observable from the site’s origin.
A possible specific approach for this
is described in
Appendix C: Example Privacy-Preserving :visited Restrictions
Allow links to match
:visited
on any origin,
but carefully restrict what styles they can apply
and what information is returned by style-querying APIs
like
getComputedStyle()
to prevent sites from observing
whether a link is styled with
:link
or
:visited
(This is documented at
MDN
and was the historical approach browsers took,
but is not perfect;
there are several ways for a hostile page
to still extract history information.)
For example, the selector
.footnote:visited
would allow styling footnote links differently
if they’ve been previously followed,
allowing users of the page to know
they might not need to click the footnote again.
8.3.
The Target Pseudo-class:
:target
In some document languages,
the document’s URL can further point to specific elements
within
the document
via the URL’s
fragment
The elements pointed to in this way are the target elements of the document.
In HTML the fragment points to the element in the page with the same ID.
The url
for example,
points to the element with
id="section2"
in the document at
The
:target
pseudo-class matches the document’s target elements.
If the document’s URL has no fragment identifier, then the document has no target elements.
Example:
p.note:target
This selector represents a
element of class
note
that is the target element of the referring
URL.
CSS example:
Here, the
:target
pseudo-class is used to make the
target element red and place an image before it, if there is one:
:target { color : red }
:target::before { content : url(target.png) }
Note:
This specification previously defined a
:target-within
pseudo-class,
analogous to
:focus-within
It was removed in favor of
:has(:target)
which should hopefully suffice to solve the same use-cases.
8.4.
The Reference Element Pseudo-class:
:scope
Tests
scope-selector.html
(live test)
(source)
scope-without-scoping.html
(live test)
(source)
In some contexts, selectors are matched
with respect to one or more
scoping roots
such as when calling the
querySelector()
method in
[DOM]
The
:scope
pseudo-class represents
this
scoping root
and may be either a true element
or a virtual one (such as a
DocumentFragment
).
If there is no
scoping root
then
:scope
represents the root of the tree the element is in
(equivalent to
:host
in a
shadow tree
or
:root
otherwise).
Specifications intending for this pseudo-class to match specific elements
rather than this tree root element
must define their
scoping root(s)
A virtual
scoping root
is some object representing the root of a document fragment,
and can be used in selector patterns to represent other elements’ relationships
to this
scoping root
acting as the parent of any root elements in the document fragment it represents.
A virtual
scoping root
is
featureless
and cannot be the
subject of the selector
For example, if you have a
DocumentFragment
df
then
df
querySelectorAll
":scope > .foo"
matches all the
.foo
elements that are "top-level" in the document fragment
(those that have the document fragment as their
parentNode
).
However,
df
querySelector
":scope"
will not match anything,
as the document fragment itself can’t be the
subject of the selector
9.
User Action Pseudo-classes
Interactive user interfaces sometimes change the rendering in response to user actions.
Selectors provides several
user action pseudo-classes
for the selection of an element the user is acting on.
(In non-interactive user agents, these pseudo-classes are valid, but never match any element.)
The
user action pseudo-classes
are not mutually exclusive.
An element can match several such pseudo-classes at the same time.
Examples:
a:hover /* user hovers over the link */
a:focus /* user focuses the link */
a:focus:hover
/* user hovers over the link while it’s focused */
Some
user action pseudo-classes
in addition to matching on the particular element with the property in question,
match on that element’s ancestors as well:
:hover
:active
:focus-within
Specifically, if these match on a given element,
they also match on the element’s
flat tree
ancestors,
up to and including the first
top layer
element
or the
root
element,
whichever is encountered first.
Note:
The specifics of hit-testing,
necessary to know when several of the pseudo-classes defined in this section apply,
are not yet defined,
but will be in the future.
9.1.
The Pointer Hover Pseudo-class:
:hover
Tests
hover-001-manual.html (manual test)
(source)
hover-002.html
(live test)
(source)
remove-hovered-element.html
(live test)
(source)
The
:hover
pseudo-class applies
while the user designates an element (or pseudo-element)
with a pointing device,
but does not necessarily activate it.
For example, a visual user agent could apply this pseudo-class
when the cursor (mouse pointer) hovers over a box generated by the element.
Interactive user agents that cannot detect hovering due to hardware limitations
(e.g., a pen device that does not detect hovering)
are still conforming;
the selector will simply never match in such a UA.
An element also matches
:hover
if one of its descendants in the
flat tree
(including non-element nodes, such as text nodes)
matches the above conditions.
Document languages may define additional ways in which an element can match
:hover
For example,
[HTML5]
defines a labeled control element as
matching
:hover
when its
label
is hovered.
Note:
Since the
:hover
state can apply to an element
because its child is designated by a pointing device,
it is possible for
:hover
to apply
to an element that is not underneath the pointing device.
9.2.
The Activation Pseudo-class:
:active
The
:active
pseudo-class
applies while an element is being “activated” by the user,
as defined by the host language;
for example, while a hyperlink is being triggered.
In addition, the
:active
pseudo-class applies
while any generated box of
any
element (or pseudo-element)
is being actively indicated by a pointing device (in the “down” state),
e.g. between the time the user presses the primary mouse button and releases it,
or while a finger is pressing on a touchscreen.
Note:
[HTML5]
defines
specific conditions for HTML elements to be activated
An element also matches
:active
if one of its descendants in the
flat tree
(including non-element nodes, such as text nodes)
matches the above conditions.
9.3.
The Input Focus Pseudo-class:
:focus
Tests
focus-display-none-001.html
(live test)
(source)
focus-in-focus-event-001.html
(live test)
(source)
focus-in-focusin-event-001.html
(live test)
(source)
The
:focus
pseudo-class applies
while an element (or pseudo-element) has the focus
(accepts keyboard or other forms of input).
There may be document language or implementation specific limits on
which elements can acquire
:focus
For example,
[HTML]
defines a list of
focusable areas
Document languages may define additional ways in which an element can match
:focus
except that the
:focus
pseudo-class must not automatically propagate to the parent element—see
:focus-within
if matching on the parent is desired.
:focus
may still apply to the parent element
if made to propagate due to other mechanisms,
but not merely due to being the parent.)
There’s a desire from authors to propagate
:focus
from a form control to its associated
label
element;
the main objection seems to be implementation difficulty.
See
CSSWG issue (CSS)
and
WHATWG issue (HTML)
9.4.
The Focus-Indicated Pseudo-class:
:focus-visible
Tests
focus-visible-001.html
(live test)
(source)
focus-visible-002.html
(live test)
(source)
focus-visible-003.html
(live test)
(source)
focus-visible-004.html
(live test)
(source)
focus-visible-005.html
(live test)
(source)
focus-visible-006.html
(live test)
(source)
focus-visible-007.html
(live test)
(source)
focus-visible-008.html
(live test)
(source)
focus-visible-009.html
(live test)
(source)
focus-visible-010.html
(live test)
(source)
focus-visible-011.html
(live test)
(source)
focus-visible-012.html
(live test)
(source)
focus-visible-013.html
(live test)
(source)
focus-visible-014.html
(live test)
(source)
focus-visible-015.html
(live test)
(source)
focus-visible-016.html
(live test)
(source)
focus-visible-017-2.html
(live test)
(source)
focus-visible-017.html
(live test)
(source)
focus-visible-018-2.html
(live test)
(source)
focus-visible-018.html
(live test)
(source)
focus-visible-019.html
(live test)
(source)
focus-visible-020.html
(live test)
(source)
focus-visible-021.html
(live test)
(source)
focus-visible-023.html
(live test)
(source)
focus-visible-024.html
(live test)
(source)
focus-visible-025.html
(live test)
(source)
focus-visible-026.html
(live test)
(source)
focus-visible-027.html
(live test)
(source)
focus-visible-028.html
(live test)
(source)
focus-visible-script-focus-001.html
(live test)
(source)
focus-visible-script-focus-004.html
(live test)
(source)
focus-visible-script-focus-005.html
(live test)
(source)
focus-visible-script-focus-008-b.html
(live test)
(source)
focus-visible-script-focus-008.html
(live test)
(source)
focus-visible-script-focus-009.html
(live test)
(source)
focus-visible-script-focus-010.html
(live test)
(source)
focus-visible-script-focus-011.html
(live test)
(source)
focus-visible-script-focus-012.html
(live test)
(source)
focus-visible-script-focus-013.html
(live test)
(source)
focus-visible-script-focus-014.html
(live test)
(source)
focus-visible-script-focus-015.html
(live test)
(source)
focus-visible-script-focus-018.html
(live test)
(source)
focus-visible-script-focus-019.html
(live test)
(source)
focus-visible-script-focus-020.html
(live test)
(source)
parse-focus-visible.html
(live test)
(source)
While the
:focus
pseudo-class
always matches the currently-focused element,
UAs only sometimes visibly
indicate focus
(such as by drawing a “focus ring”),
instead using a variety of heuristics
to visibly indicate the focus only when it would be most helpful to the user.
The
:focus-visible
pseudo-class
matches a focused element (or pseudo-element)
in these situations only,
allowing authors to change the appearance of the focus indicator
without changing
when
a focus indicator appears.
In this example,
all focusable elements get a strong yellow outline on
:focus-visible
and links get both a yellow outline and a yellow background on
:focus-visible
These styles are consistent throughout the page and are easily visible
due to their bold styling,
but do not appear unless the user is likely to need to understand
where page focus is.
:root
--focus-gold
#ffbf47
:focus-visible
outline
px
solid
var
--focus-gold
);
a:focus-visible
background-color
var
--focus-gold
);
User agents can choose their own heuristics for when to
indicate focus
however, the following (non-normative) suggestions can be used as a starting point
for when to
indicate focus
on the currently focused element:
If the user has expressed a preference
(such as via a system preference or a browser setting)
to always see a visible focus indicator,
indicate focus
regardless of any other factors.
(Another option may be for the user agent to show its own focus indicator
regardless of author styles.)
If the element which supports keyboard input
(such as an
input
element,
or any other element
that would triggers a virtual keyboard to be shown on focus
if a physical keyboard were not present),
indicate focus
If the user interacts with the page via keyboard or some other non-pointing device,
indicate focus
(This means keyboard usage may change whether this pseudo-class matches
even if it doesn’t affect
:focus
).
If the user interacts with the page via a pointing device (mouse, touchscreen, etc.)
and the focused element does not support keyboard input,
don’t
indicate focus
If the previously-focused element
indicated focus
and a script causes focus to move elsewhere,
indicate focus
on the newly focused element.
Conversely, if the previously-focused element did not
indicate focus
and a script causes focus to move elsewhere,
don’t
indicate focus
on the newly focused element.
If a newly-displayed element automatically gains focus
(such as an action button in a freshly opened dialog),
that element should
indicate focus
User agents should also use
:focus-visible
to specify the default focus style,
so that authors using
:focus-visible
will not also need to disable
the default
:focus
style.
9.5.
The Focus Container Pseudo-class:
:focus-within
Tests
focus-within-001.html
(live test)
(source)
focus-within-002.html
(live test)
(source)
focus-within-003.html
(live test)
(source)
focus-within-004.html
(live test)
(source)
focus-within-005.html
(live test)
(source)
focus-within-006.html
(live test)
(source)
focus-within-007.html
(live test)
(source)
focus-within-008.html
(live test)
(source)
focus-within-009.html
(live test)
(source)
focus-within-010.html
(live test)
(source)
focus-within-011.html
(live test)
(source)
focus-within-012.html
(live test)
(source)
focus-within-013.html
(live test)
(source)
focus-within-display-none-001.html
(live test)
(source)
focus-within-focus-move.html
(live test)
(source)
focus-within-removal.html
(live test)
(source)
focus-within-shadow-001.html
(live test)
(source)
focus-within-shadow-002.html
(live test)
(source)
focus-within-shadow-003.html
(live test)
(source)
focus-within-shadow-004.html
(live test)
(source)
focus-within-shadow-005.html
(live test)
(source)
focus-within-shadow-006.html
(live test)
(source)
The
:focus-within
pseudo-class
applies to any element (or pseudo-element)
for which the
:focus
pseudo-class applies,
as well as to an element (or pseudo-element)
whose descendant in the
flat tree
(including non-element nodes, such as text nodes)
matches the conditions for matching
:focus
10.
Resource State Pseudo-classes
The pseudo-classes in this section apply to elements that represent loaded resources,
particularly images/videos,
and allow authors to select them based on some quality of their state.
10.1.
Media Playback State: the
:playing
:paused
, and
:seeking
pseudo-classes
Tests
media-playback-state.html
(live test)
(source)
The
:playing
pseudo-class represents an element
that is capable of being “played” or “paused”,
when that element is “playing”.
(This includes both when the element is explicitly playing,
and when it’s temporarily stopped for some reason not connected to user intent,
but will automatically resume when that reason is resolved,
such as a “buffering” or “stalled” state.)
The
:paused
pseudo-class represents an element
that is capable of being “played” or “paused”,
when that element is “paused” (i.e.
not
”playing”).
(This includes both an explicit “paused” state,
and other non-playing states like “loaded, hasn’t been activated yet”, etc.)
The
:seeking
pseudo-class represents an element
that is capable of ”seeking”
when that element is ”seeking”.
(For the
audio
and
video
elements of HTML, see
HTML
§ 4.8.11.9 Seeking
.)
10.2.
Media Loading State: the
:buffering
and
:stalled
pseudo-classes
Tests
media-loading-state.html
(live test)
(source)
media-loading-state-timing.sub.html
(live test)
(source)
media-playback-state-timing.html
(live test)
(source)
The
:buffering
pseudo-class represents an element
that is capable of being “played” or “paused”,
when that element cannot continue playing
because it is actively attempting to obtain
media data
but has not yet obtained enough data to resume playback.
(Note that the element is still considered to be “playing” when it is “buffering”.
Whenever
:buffering
matches an element,
:playing
also matches the element.)
The
:stalled
pseudo-class represents an element
when that element cannot continue playing
because it is actively attempting to obtain
media data
but it has failed to receive any data for some amount of time.
For the
audio
and
video
elements of HTML,
this amount of time is the
media element stall timeout
[HTML]
(Note that, like with the
:buffering
pseudo-class,
the element is still considered to be “playing” when it is “stalled”.
Whenever
:stalled
matches an element,
:playing
also matches the element.)
10.3.
Sound State: the
:muted
and
:volume-locked
pseudo-classes
Tests
sound-state.html
(live test)
(source)
The
:muted
pseudo-class represents
an element that is capable of making sound,
but is currently “muted“ (forced silent).
(For the
audio
and
video
elements of HTML, see
muted
[HTML]
The
:volume-locked
pseudo-class represents
an element that is capable of making sound,
and currently has its volume "locked"
by the UA or the user,
so the page author cannot change it.
(For the
audio
and
video
elements of HTML,
see the algorithm for setting the element’s
effective media volume
[HTML]
11.
Element Display State Pseudo-classes
11.1.
Collapse State: the
:open
pseudo-class
Tests
open-pseudo.html
(live test)
(source)
details-open-pseudo-001.html
(live test)
(source)
details-open-pseudo-002.html
(live test)
(source)
details-open-pseudo-003.html
(live test)
(source)
input-element-pseudo-open.optional.html
(live test)
(source)
The
:open
pseudo-class represents an element
that has both “open” and “closed” states,
and which is currently in the “open” state.
Exactly what “open” and “closed” mean is host-language specific,
but exemplified by elements such as
HTML’s
details
select
dialog
, and
input
elements,
all of which can be toggled “open” to display more content
(or any content at all, in the case of
dialog
).
Note:
Being “open” or “closed” is a semantic state.
An element not currently being displayed
(for example, one that has
visibility: collapse
or belongs to a
display: none
subtree)
can still be “open” and will match
:open
Note:
A ":closed" pseudo-class might be added in the future
once the full set of things that support
:open
is known.
11.2.
Popover State: the
:popover-open
pseudo-class
Tests
popover-open-with-has-sibling-selector.html
(live test)
(source)
The
:popover-open
pseudo-class represents an element
that has both “popover-showing” and “popover-hidden” states
and which is currently in the “popover-showing” state.
Note:
This is distinct from
:open
because
an element can have element-specific open and closed states
and also have separate popover-showing and popover-hidden states
associated with being a popover.
Exactly what “popover-showing” and “popover-hidden” states
mean is host-language specific,
but is exemplified by the presence of the HTML
popover
attribute
and the associated
popover visibility state
11.3.
Modal (Exclusive Interaction) State: the
:modal
pseudo-class
Tests
modal-pseudo-class.html
(live test)
(source)
The
:modal
pseudo-class represents
an element which is in a state that excludes all interaction
with elements outside it until it has been dismissed.
Multiple elements can be
:modal
simultaneously,
with only one of them active (able to receive input).
For example, the
dialog
element is
:modal
when opened with the
showModal()
API.
Similarly, a
:fullscreen
element is also
:modal
when opened with the
requestFullscreen()
API,
since this prevents interaction with the rest of the page.
11.4.
Fullscreen Presentation State: the
:fullscreen
pseudo-class
The
:fullscreen
pseudo-class represents
an element which is displayed in a mode that
takes up most (usually all) of the screen,
such as that defined by the Fullscreen API.
[FULLSCREEN]
11.5.
Picture-in-Picture Presentation State: the
:picture-in-picture
pseudo-class
The
:picture-in-picture
pseudo-class represents
an element which is displayed in a mode that
takes up most (usually all) of the viewport,
and whose viewport is confined to part of the screen
while being displayed over other content,
for example when using the Picture-in-Picture API.
[picture-in-picture]
12.
The Input Pseudo-classes
The pseudo-classes in this section mostly apply to elements that take user input,
such as HTML’s
input
element.
12.1.
Input Control States
12.1.1.
The
:enabled
and
:disabled
Pseudo-classes
Tests
enabled-disabled.html
(live test)
(source)
pseudo-enabled-disabled.html
(live test)
(source)
The
:enabled
pseudo-class represents
user interface elements that are in an enabled state;
such elements must have a corresponding disabled state.
Conversely, the
:disabled
pseudo-class represents
user interface elements that are in a disabled state;
such elements must have a corresponding enabled state.
What constitutes an enabled state, a disabled state, and a user interface
element is host-language-dependent. In a typical document most elements will be
neither
:enabled
nor
:disabled
For example,
[HTML5]
defines
non-disabled interactive elements
to be
:enabled
and any such elements that are
explicitly disabled
to be
:disabled
Note:
CSS properties that might affect a user’s ability
to interact with a given user interface element do not affect whether it
matches
:enabled
or
:disabled
; e.g., the
display
and
visibility
properties have no effect
on the enabled/disabled state of an element.
12.1.2.
The Mutability Pseudo-classes:
:read-only
and
:read-write
Tests
selector-read-write-type-change-001.html
(live test)
(source)
selector-read-write-type-change-002.html
(live test)
(source)
An element matches
:read-write
if it is user-alterable,
as defined by the document language.
Otherwise, it is
:read-only
For example, in
[HTML5]
non-disabled non-readonly
element
is
:read-write
as is any element with the
contenteditable
attribute set to the true state.
12.1.3.
The Placeholder-shown Pseudo-class:
:placeholder-shown
Tests
placeholder-shown.html
(live test)
(source)
placeholder-shown.html
(live test)
(source)
selector-placeholder-shown-emptify-placeholder.html
(live test)
(source)
selector-placeholder-shown-type-change-001.html
(live test)
(source)
selector-placeholder-shown-type-change-002.html
(live test)
(source)
selector-placeholder-shown-type-change-003.html
(live test)
(source)
Input elements can sometimes show placeholder text
as a hint to the user on what to type in.
See, for example, the
placeholder
attribute in
[HTML5]
The
:placeholder-shown
pseudo-class
matches an input element that is showing such placeholder text,
whether that text is given by an attribute or a real element,
or is otherwise implied by the UA.
For example, according to the semantics of
[HTML]
the
placeholder
attribute on the
input
and
textarea
elements
provide placeholder text.
The
:placeholder-shown
class thus applies
whenever such placeholder text is shown.
12.1.4.
The Automatic Input Pseudo-class:
:autofill
The
:autofill
pseudo-class represents input elements
that have been automatically filled by the user agent,
and have not been subsequently altered by the user.
12.1.5.
The Default-option Pseudo-class:
:default
The
:default
pseudo-class applies to the one or more UI elements
that are the default among a set of similar elements. Typically applies to
context menu items, buttons and select lists/menus.
One example is the default submit button among a set of buttons.
Another example is the default option from a popup menu.
In a select-many group (such as for pizza toppings), multiple elements can match
:default
For example,
[HTML5]
defines that
:default
matches
the “default button” in a form,
the initially-selected