Selectors Level 4
Selectors Level 4
Editor’s Draft
22 April 2026
More details about this document
This version:
Latest published version:
Previous Versions:
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 is a public copy of the editors’ draft.
It is provided for discussion only and may change at any moment.
Its publication here does not imply endorsement of its contents by W3C.
Don’t cite this document other than as 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
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(sr, "*-Cyrl")
an element of type E tagged as being in Serbian,
(which typically uses Cyrillic, but can be written with Latin characters)
but also anything written with Cyrillic 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)
input-in-range-in-has-with-readonly.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.sub.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)
open-pseudo-class-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 { ... }
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-attr-many-2.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]
).
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).
For example, ASCII case insensitivity allows
green
to match
GREEN
However,
grün
would not match
GRÜN
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)
lang-singleton-subtag-matching.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()
is an
extended language range
as defined in BCP 47, and
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
ASCII case-insensitively
The
language range
must be an extended language range according to BCP47.
Language ranges that are not
well-formed
language tags
or which would not be a well-formed language tag
if an initial wildcard character "*"
were replaced with a valid subtag,
do not match anything.
For example,
:lang
åå
would not match,
because it containins non-ASCII characters so is ill-formed.
On the other hand,
:lang
qq
could match,
even though qq is not a registered language code.
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 language tags from
[BCP47]
and in the case of XML-based formats, by means of
xml:lang
attributes.
[XML10]
See
“Choosing a Language Tag”
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.

Je suis français.



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.
Tests
active-toplayer-001.html
(live test)
(source)
focus-within-toplayer-001.html
(live test)
(source)
hover-toplayer-001.html
(live test)
(source)
toplayer-transition-001.html
(live test)
(source)
user-action-pseudo-top-layer.html
(live test)
(source)
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)
media-loading-state.sub.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-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



...

13.
Tree-Structural pseudo-classes
Tests
selector-structural-pseudo-root.html
(live test)
(source)
Selectors introduces the concept of
structural pseudo-classes
to permit selection based on extra information that lies in
the document tree but cannot be represented by other simple selectors or
combinators.
Standalone text and other non-element
nodes are not counted when calculating the position of an element in the list
of children of its parent. When calculating the position of an element in
the list of children of its parent, the index numbering starts at 1.
The
structural pseudo-classes
only apply to elements in the document tree;
they must never match
pseudo-elements
13.1.
:root
pseudo-class
Tests
root-siblings.html
(live test)
(source)
The
:root
pseudo-class represents an element that is
the root of the document.
For example, in a DOM document,
the
:root
pseudo-class matches the
document element
In HTML, this will be the
html
element
(unless scripting has been used to modify the document).
13.2.
:empty
pseudo-class
Tests
selectors-empty-001.xml
(live test)
(source)
The
:empty
pseudo-class represents
an element that has no children
except, optionally,
document white space characters
In terms of the document tree,
only element nodes and content nodes
(such as
[DOM]
text nodes, and entity references)
whose data has a non-zero length must be considered as affecting emptiness;
comments, processing instructions, and other nodes
must not affect whether an element is considered empty or not.
Examples:
p:empty
is a valid representation of the
elements
in the following HTML fragment:





div:empty
is not a valid representation of the

elements
in the following fragment:
text


 

bla


this is not

:empty


Note:
In Level 2 and Level 3 of Selectors,
:empty
did not match elements that contained only white space.
This was changed so that that—​given white space is largely collapsible in HTML
and is therefore used for source code formatting,
and especially because elements with omitted end tags
are likely to absorb such white space into their DOM text contents—​elements which authors perceive of as empty
can be selected by this selector, as they expect.
13.3.
Child-indexed Pseudo-classes
Tests
child-indexed-no-parent.html
(live test)
(source)
child-indexed-pseudo-class.html
(live test)
(source)
negated-nth-child-when-ancestor-changes.html
(live test)
(source)
negated-nth-last-child-when-ancestor-changes.html
(live test)
(source)
nth-child-containing-ancestor.html
(live test)
(source)
nth-child-in-shadow-root.html
(live test)
(source)
nth-child-of-attr-largedom.html
(live test)
(source)
nth-child-of-attr.html
(live test)
(source)
nth-child-of-class-prefix.html
(live test)
(source)
nth-child-of-class.html
(live test)
(source)
nth-child-of-has.html
(live test)
(source)
nth-child-of-id-prefix.html
(live test)
(source)
nth-child-of-ids.html
(live test)
(source)
nth-child-of-in-ancestor.html
(live test)
(source)
nth-child-of-in-is.html
(live test)
(source)
nth-child-of-in-shadow-root.html
(live test)
(source)
nth-child-of-is.html
(live test)
(source)
nth-child-of-pseudo-class.html
(live test)
(source)
nth-child-of-sibling.html
(live test)
(source)
nth-child-when-ancestor-changes.html
(live test)
(source)
nth-child-when-sibling-changes.html
(live test)
(source)
nth-child-whole-subtree.html
(live test)
(source)
nth-last-child-containing-ancestor.html
(live test)
(source)
nth-last-child-in-shadow-root.html
(live test)
(source)
nth-last-child-of-attr.html
(live test)
(source)
nth-last-child-of-class-prefix.html
(live test)
(source)
nth-last-child-of-class.html
(live test)
(source)
nth-last-child-of-has.html
(live test)
(source)
nth-last-child-of-id-prefix.html
(live test)
(source)
nth-last-child-of-ids.html
(live test)
(source)
nth-last-child-of-in-ancestor.html
(live test)
(source)
nth-last-child-of-in-is.html
(live test)
(source)
nth-last-child-of-in-shadow-root.html
(live test)
(source)
nth-last-child-of-is.html
(live test)
(source)
nth-last-child-of-pseudo-class.html
(live test)
(source)
nth-last-child-of-sibling.html
(live test)
(source)
nth-last-child-when-ancestor-changes.html
(live test)
(source)
nth-last-child-when-sibling-changes.html
(live test)
(source)
nth-child-and-nth-last-child.html
(live test)
(source)
nth-child-of-attribute.html
(live test)
(source)
nth-child-of-classname-002.html
(live test)
(source)
nth-child-of-classname.html
(live test)
(source)
nth-child-of-complex-selector-many-children-2.html
(live test)
(source)
nth-child-of-complex-selector-many-children.html
(live test)
(source)
nth-child-of-complex-selector.html
(live test)
(source)
nth-child-of-compound-selector.html
(live test)
(source)
nth-child-of-has.html
(live test)
(source)
nth-child-of-nesting.html
(live test)
(source)
nth-child-of-no-space-after-of.html
(live test)
(source)
nth-child-of-not.html
(live test)
(source)
nth-child-of-nth-child.html
(live test)
(source)
nth-child-of-pseudo.html
(live test)
(source)
nth-child-of-tagname.html
(live test)
(source)
nth-child-of-universal-selector.html
(live test)
(source)
nth-child-specificity-1.html
(live test)
(source)
nth-child-specificity-2.html
(live test)
(source)
nth-child-specificity-3.html
(live test)
(source)
nth-child-specificity-4.html
(live test)
(source)
nth-child-spurious-brace-crash.html
(live test)
(source)
nth-last-child-invalid.html
(live test)
(source)
nth-last-child-of-classname.html
(live test)
(source)
nth-last-child-of-complex-selector.html
(live test)
(source)
nth-last-child-of-compound-selector.html
(live test)
(source)
nth-last-child-of-nesting.html
(live test)
(source)
nth-last-child-of-no-space-after-of.html
(live test)
(source)
nth-last-child-of-style-sharing-1.html
(live test)
(source)
nth-last-child-of-style-sharing-2.html
(live test)
(source)
nth-last-child-of-tagname.html
(live test)
(source)
nth-last-child-specificity-1.html
(live test)
(source)
nth-last-child-specificity-2.html
(live test)
(source)
nth-last-child-specificity-3.html
(live test)
(source)
nth-last-child-specificity-4.html
(live test)
(source)
sharing-in-svg-use.html
(live test)
(source)
parse-anplusb.html
(live test)
(source)
The pseudo-classes defined in this section select elements
based on their index amongst their
inclusive siblings
Note:
Selectors 3 described these selectors as selecting elements based on their index in the child list of their parents.
(This description survives in the name of this very section, and the names of several of the pseudo-classes.)
As there was no reason to exclude them from matching elements without parents,
or with non-element parents,
they have been rephrased to refer to an element’s relative index amongst its siblings.
13.3.1.
:nth-child()
pseudo-class
Tests
nth-of-invalid.html
(live test)
(source)
nth-child-of-attribute-crash.html
(live test)
(source)
nth-of-namespace-class-invalidation-crash.html
(live test)
(source)
The
:nth-child(
An+B
[of
]? )
pseudo-class notation represents elements that
are among
An+B
th elements
from the list composed of
their
inclusive siblings
that match the
selector list
which is a

If
is omitted,
it defaults to
*|*
The
An+B
notation and its interpretation
are defined in
CSS Syntax 3
§ 6 The An+B microsyntax
it represents any index
for any non-negative integer
Note:
For these purposes, the list of elements is
1-indexed
that is, the first child of an element has index 1, and will be matched by
:nth-child(2n+1)
because when
n=0
the expression evaluates to
For example, this selector could address every other row in a table,
and could be used to alternate the color of paragraph text in a cycle of four.
Examples:
:nth-child(even) /* represents the 2nd, 4th, 6th, etc elements
:nth-child(10n-1) /* represents the 9th, 19th, 29th, etc elements */
:nth-child(10n+9) /* Same */
:nth-child(10n+-1) /* Syntactically invalid, and would be ignored */
Note:
The specificity of the
:nth-child()
pseudo-class is
the specificity of a single pseudo-class plus,
if
is specified,
the specificity of the most specific
complex selector
in
See
§ 15 Calculating a selector’s specificity
Thus
:nth-child(
An+B
and
:nth-child(
An+B
of
have the exact same specificity,
although they do differ in behavior
(see example below).
By passing a selector argument,
we can select the Nth element that matches that selector.
For example, the following selector matches the first three “important” list items,
denoted by the
.important
class:
:nth-child(-n+3 of li.important)
Note that this is different from moving the selector outside of the function, like:
li.important:nth-child(-n+3)
This selector instead just selects the first three children
if they also happen to be "important" list items.
Here’s another example of using the selector argument,
to ensure that zebra-striping a table works correctly.
Normally, to zebra-stripe a table’s rows,
an author would use CSS similar to the following:
tr {
background: white;
tr:nth-child(even) {
background: silver;
However, if some of the rows are hidden and not displayed,
this can break up the pattern,
causing multiple adjacent rows to have the same background color.
Assuming that rows are hidden with the
[hidden]
attribute in HTML,
the following CSS would zebra-stripe the table rows robustly,
maintaining a proper alternating background
regardless of which rows are hidden:
tr {
background: white;
tr:nth-child(even of :not([hidden])) {
background: silver;
13.3.2.
:nth-last-child()
pseudo-class
The
:nth-last-child(
An+B
[of
]? )
pseudo-class notation represents elements that
are among
An+B
th elements
from the list composed of
their
inclusive siblings
that match the
selector list
counting backwards from the end.
is

If
is omitted,
it defaults to
*|*
Note:
The specificity of the
:nth-last-child()
pseudo-class,
like the
:nth-child()
pseudo-class,
combines the specificity of a regular pseudo-class
with that of its selector argument
See
§ 15 Calculating a selector’s specificity
The CSS Syntax Module
[CSS3SYN]
defines the
An+B
notation
Examples:
tr:nth-last-child(-n+2) /* represents the two last rows of an HTML table */

foo:nth-last-child(odd) /* represents all odd foo elements in their parent element,
counting from the last one */
13.3.3.
:first-child
pseudo-class
Tests
first-child.html
(live test)
(source)
first-child-last-child.html
(live test)
(source)
The
:first-child
pseudo-class
represents an element that is first among its
inclusive siblings
Same as
:nth-child(1)
Examples:
The following selector represents a
element that is
the first child of a
div
element:
div > p:first-child
This selector can represent the
inside the
div
of the following fragment:

The last P before the note.



The first P inside the note.



but cannot represent the second
in the following fragment:

The last P before the note.



Note


The first P inside the note.



The following two selectors are usually equivalent:
* > a:first-child /* a is first child of any element */
a:first-child /* Same (assuming a is not the root element) */
13.3.4.
:last-child
pseudo-class
Tests
last-child.html
(live test)
(source)
The
:last-child
pseudo-class
represents an element that is last among its
inclusive siblings
Same as
:nth-last-child(1)
Example:
The following selector represents a list item
li
that
is the last child of an ordered list
ol
ol > li:last-child
13.3.5.
:only-child
pseudo-class
Tests
only-child.html
(live test)
(source)
The
:only-child
pseudo-class
represents an element that has no siblings.
Same as
:first-child:last-child
or
:nth-child(1):nth-last-child(1)
but with a lower specificity.
13.4.
Typed Child-indexed Pseudo-classes
Tests
nth-of-type-namespace.html
(live test)
(source)
The pseudo-classes in this section are similar to the
Child Index Pseudo-classes
but they resolve based on an element’s index
among elements of the same
type (tag name)
in their sibling list.
13.4.1.
:nth-of-type()
pseudo-class
The
:nth-of-type(
An+B
pseudo-class notation
represents the same elements that would be matched by
:nth-child(|An+B| of
where
is a
type selector
and namespace prefix matching the element in question.
For example,
when considering whether an HTML
img
element matches this
pseudo-class
the
in question is
html|img
(assuming an appropriate
html
namespace is declared).
CSS example:
This allows an author to alternate the position of floated images:
img:nth-of-type(2n+1) { float: right; }
img:nth-of-type(2n) { float: left; }
Note:
If the type of the element is known ahead of time,
this pseudo-class is equivalent to using
:nth-child()
with a type selector.
That is,
img:nth-of-type(2)
is equivalent to
*:nth-child(2 of img)
13.4.2.
:nth-last-of-type()
pseudo-class
Tests
last-of-type.html
(live test)
(source)
The
:nth-last-of-type(
An+B
pseudo-class notation
represents the same elements that would be matched by
:nth-last-child(|An+B| of
where
is a
type selector
and namespace prefix matching the element in question.
For example,
when considering whether an HTML
img
element matches this
pseudo-class
the
in question is
html|img
(assuming an appropriate
html
namespace is declared).
Example:
To represent all
h2
children of an XHTML
body
except the first and last, one could use the
following selector:
body > h2:nth-of-type(n+2):nth-last-of-type(n+2)
In this case, one could also use
:not()
, although the
selector ends up being just as long:
body > h2:not(:first-of-type):not(:last-of-type)
13.4.3.
:first-of-type
pseudo-class
Tests
first-of-type.html
(live test)
(source)
negated-always-matches-negated-first-of-type-when-ancestor-changes.html
(live test)
(source)
negated-first-of-type-in-nonsubject-position.html
(live test)
(source)
negated-is-always-matches-negated-first-of-type-when-ancestor-changes.html
(live test)
(source)
negated-is-never-matches-negated-first-of-type-when-ancestor-changes.html
(live test)
(source)
negated-negated-first-of-type-when-ancestor-changes.html
(live test)
(source)
negated-never-matches-negated-first-of-type-when-ancestor-changes.html
(live test)
(source)
of-type-selectors.xhtml
(live test)
(source)
The
:first-of-type
pseudo-class
represents the same element as
:nth-of-type(1)
Example:
The following selector represents a definition title
dt
inside a definition list
dl
, this
dt
being the first of its type in the list of children of
its parent element.
dl dt:first-of-type
It is a valid description for the first two
dt
elements in the following example but not for the third one:

gigogne



fusée

multistage rocket

table

nest of tables




13.4.4.
:last-of-type
pseudo-class
Tests
negated-always-matches-negated-last-of-type-when-ancestor-changes.html
(live test)
(source)
negated-is-always-matches-negated-last-of-type-when-ancestor-changes.html
(live test)
(source)
negated-is-never-matches-negated-last-of-type-when-ancestor-changes.html
(live test)
(source)
negated-last-of-type-invalidation.html
(live test)
(source)
negated-negated-last-of-type-when-ancestor-changes.html
(live test)
(source)
negated-never-matches-negated-last-of-type-when-ancestor-changes.html
(live test)
(source)
The
:last-of-type
pseudo-class
represents the same element as
:nth-last-of-type(1)
Example:
The following selector represents the last data cell
td
of a table row
tr
tr > td:last-of-type
13.4.5.
:only-of-type
pseudo-class
Tests
only-of-type.html
(live test)
(source)
The
:only-of-type
pseudo-class
represents the same element as
:first-of-type:last-of-type
14.
Combinators
14.1.
Descendant combinator (
Tests
parse-descendant.html
(live test)
(source)
At times, authors may want selectors to describe an element that is
the descendant of another element in the document tree (e.g., "an
em
element that is contained within an
H1
element").
The
descendant combinator
expresses such a relationship.
A descendant combinator is whitespace that separates two
compound selectors
A selector of the form
A B
represents an element
that is an
arbitrary descendant of some ancestor element
Examples:
For example, consider the following selector:
h1 em
It represents an
em
element being the descendant of
an
h1
element. It is a correct and valid, but partial,
description of the following fragment:

This headline
is very important


The following selector:
div * p
represents a
element that is a grandchild or later
descendant of a
div
element. Note the whitespace on
either side of the "*" is not part of the universal selector; the
whitespace is a combinator indicating that the
div
must be the
ancestor of some element, and that that element must be an ancestor
of the
The following selector, which combines descendant combinators and
attribute selectors
, represents an
element that (1) has the
href
attribute set and (2) is
inside a
that is itself inside a
div
div p *[href]
14.2.
Child combinator (
Tests
parse-child.html
(live test)
(source)
child combinator
describes a childhood relationship
between two elements. A child combinator is made of the
"greater-than sign" (U+003E,
) code point and
separates two
compound selectors
Examples:
The following selector represents a
element that is
child of
body
body > p
The following example combines descendant combinators and child
combinators.
div ol>li p
It represents a
element that is a descendant of an
li
element; the
li
element must be the
child of an
ol
element; the
ol
element must
be a descendant of a
div
. Notice that the optional white
space around the ">" combinator has been left out.
For information on selecting the first child of an element,
please see the section on the
:first-child
pseudo-class above.
14.3.
Next-sibling combinator (
Tests
insert-sibling-001.html
(live test)
(source)
insert-sibling-002.html
(live test)
(source)
insert-sibling-003.html
(live test)
(source)
insert-sibling-004.html
(live test)
(source)
sibling.html
(live test)
(source)
parse-sibling.html
(live test)
(source)
The
next-sibling combinator
is made of the “plus sign”
(U+002B,
) code point that separates two
compound selectors
The elements represented by the two
compound selectors
share the same parent in the document tree
and the element represented by the first
compound selector
immediately precedes the element represented by the second one.
Non-element nodes (e.g. text between elements)
are ignored when considering the adjacency of elements.
Examples:
The following selector represents a
element
immediately following a
math
element:
math + p
The following selector is conceptually similar to the one in the
previous example, except that it adds an attribute selector — it
adds a constraint to the
h1
element, that it must have
class="opener"
h1.opener + h2
14.4.
Subsequent-sibling combinator (
The
subsequent-sibling combinator
is made of the "tilde"
(U+007E,
) code point that separates two
compound selectors
The elements represented by the two
compound selectors
share
the same parent in the document tree and the element represented by
the first compound selector precedes (not necessarily immediately) the element
represented by the second one.
h1 ~ pre
represents a
pre
element following an
h1
. It
is a correct and valid, but partial, description of:

Definition of the function a


Function a(x) has to be applied to all figures in the table.


function a(x) = 12x/13.5

15.
Calculating a selector’s specificity
A selector’s
specificity
is calculated for a given element as follows:
count the number of ID selectors in the selector (=
count the number of class selectors, attributes selectors, and pseudo-classes in the selector (=
count the number of type selectors and pseudo-elements in the selector (=
ignore the universal selector
If the selector is a
selector list
this number is calculated for each selector in the list.
For a given matching process against the list, the specificity in effect
is that of the most specific selector in the list that matches.
A few pseudo-classes provide “evaluation contexts” for other selectors,
and so have their specificity defined specially:
The specificity of an
:is()
:not()
, or
:has()
pseudo-class
is replaced by the specificity of
the most specific
complex selector
in its
selector list
argument.
Analogously, the specificity of an
:nth-child()
or
:nth-last-child()
selector
is the specificity of the pseudo-class itself (counting as one pseudo-class selector)
plus the specificity of
the most specific
complex selector
in its
selector list
argument (if any).
The specificity of a
:where()
pseudo-class is replaced by zero.
For example:
:is(em, #foo)
has
a specificity of (1,0,0)—​like an ID selector (
#foo
)—​when matched against any of


, or

.qux:where(em, #foo#bar#baz)
has
a specificity of (0,1,0):
only the
.qux
outside the
:where()
contributes to selector specificity.
:nth-child(even of li, .item)
has
a specificity of (0,2,0)—​like a class selector (
.item
) plus a pseudo-class—​when matched against any of



    • , or

    • :not(em, strong#foo)
      has
      a specificity of (1,0,1)—​like a tag selector (
      strong
      ) combined with an ID selector (
      #foo
      )—​when matched against any element.
      Specificities are compared by comparing the three components in order:
      the specificity with a larger
      value is more specific;
      if the two
      values are tied,
      then the specificity with a larger
      value is more specific;
      if the two
      values are also tied,
      then the specificity with a larger
      value is more specific;
      if all the values are tied,
      the two specificities are equal.
      Due to storage limitations,
      implementations may have limitations on the size of
      , or
      If so, values higher than the limit must be clamped to that limit,
      and not overflow.
      Examples:
      * /* a=0 b=0 c=0 */
      LI /* a=0 b=0 c=1 */
      UL LI /* a=0 b=0 c=2 */
      UL OL+LI /* a=0 b=0 c=3 */
      H1 + *[REL=up] /* a=0 b=1 c=1 */
      UL OL LI.red /* a=0 b=1 c=3 */
      LI.red.level /* a=0 b=2 c=1 */
      #x34y /* a=1 b=0 c=0 */
      #s12:not(FOO) /* a=1 b=0 c=1 */
      .foo :is(.bar, #baz)
      /* a=1 b=1 c=0 */
      Note:
      Repeated occurrences of the
      same simple selector are allowed and do increase specificity.
      Note:
      The specificity of the styles
      specified in an HTML
      style
      attribute
      is described in CSS Style Attributes
      [CSSSTYLEATTR]
      16.
      Grammar
      Tests
      selectors-attr-white-space-001.html
      (live test)
      (source)
      Selectors are
      parsed
      according to the following grammar:



















      = [













      = [









      = '>'
      '+'
      '~'




      = [

      '*' ]
      '|'



      '*'








      = '.'


      = '['

      ']'
      '['





      ']'

      = [ '~'
      '|'
      '^'
      '$'
      '*' ]
      '='

      = i

      = :




      = :



      = : [before
      after
      first-line
      first-letter]
      In interpreting the above grammar,
      the following rules apply:
      White space is forbidden:
      Between any of the top-level components of a

      or

      (that is, forbidden between the

      and

      or between the

      and

      etc).
      Between
      any
      of the components of a

      or a

      Between the ':'s, or between the ':' and

      or

      of a

      or a

      Between
      any
      of the components of a

      Between the components of an

      Between the

      or

      in a

      Whitespace is
      required
      between two

      if the

      between them is omitted.
      (This indicates the descendant combinator is being used.)
      In

      , the

      ’s value must be an
      identifier
      The

      production
      excludes the

      production.
      (That is,
      :before
      /etc must never be parsed as a pseudo-class,
      even if doing so would cause the selector to become valid
      due to, for example, other simple selectors following it.)
      Note:
      A selector is also subject to a variety of more specific syntactic constraints,
      and adherence to the grammar above is necessary
      but not sufficient
      for the selector to be considered valid.
      See
      § 3.9 Invalid Selectors and Error Handling
      for additional rules for parsing selectors.
      Note:
      In general,

      is only valid
      if placed at the end of the last

      in a

      In some circumstances, however,
      it can be followed by more

      s or

      s;
      but these are specified on a case-by-case basis.
      (For example, the
      user action pseudo-classes
      are allowed after any
      pseudo-element
      and the
      tree-abiding pseudo-elements
      are allowed after the
      ::slotted()
      pseudo-element.)
      The four
      Level 2
      pseudo-elements
      ::before
      ::after
      ::first-line
      , and
      ::first-letter
      may, for legacy reasons,
      be written with only a single ":" character at their front,
      making them resemble a

      16.1.

      For legacy reasons,
      the general behavior of a selector list
      is that if any selector in the list fails to parse
      (because it uses new or UA-specific selector features, for instance),
      the entire selector list becomes invalid.
      This can make it hard to write CSS that uses new selectors
      and still works correctly in older user agents.
      The

      production
      instead parses each selector in the list individually,
      simply ignoring ones that fail to parse,
      so the remaining selectors can still be used.
      Note:
      Style rules still use the normal, unforgiving selector list behavior.

      is used in
      :is()
      and
      :where()
      only.
      Although it does have some minor implications on specificity,
      wrapping a style rule’s selector in
      :is()
      effectively "upgrades" it to become forgiving,
      so long as it doesn’t contain any pseudo-elements
      (which aren’t valid in
      :is()
      or
      :where()
      ).
      Syntactically,

      is equivalent to

      It is then
      parsed as a forgiving selector list
      to obtain its actual value.
      To
      parse as a forgiving selector list
      given an input
      input
      Parse a list
      of

      s from
      input
      and let
      selector list
      be the result.
      Remove all failure items from
      selector list
      and all items that are
      invalid selectors
      then return a

      representing the remaining items in
      selector list
      (This might be empty.)
      Any items in a

      that are invalid
      (whether explicitly, by using unknown selectors or syntax,
      or merely contextually, using known syntax but in an invalid context)
      must be treated as having zero specificity.
      Note:

      is intentionally used only in
      :is()
      and
      :where()
      not in any other selector that takes a selector argument.
      17.
      API Hooks
      To aid in the writing of specs that use Selectors concepts,
      this section defines several API hooks that can be invoked by other specifications.
      Are these still necessary now that we have more rigorous definitions for
      match
      and
      invalid selector
      Nouns are a lot easier to coordinate across specification than predicates,
      and details like the exact order of elements returned from
      querySelector
      seem to make more sense being defined in the DOM specification than in Selectors.
      17.1.
      Parse A Selector
      This section defines how to
      parse a selector
      from a string
      source
      It returns either a complex selector list,
      or failure.
      Let
      selector
      be the result of
      parsing
      source
      as a

      If this returns failure,
      it’s an
      invalid selector
      return failure.
      If
      selector
      is an
      invalid selector
      for any other reason
      (such as, for example, containing an undeclared namespace prefix),
      return failure.
      Otherwise,
      return
      selector
      17.2.
      Parse A Relative Selector
      This section defines how to
      parse a relative selector
      from a string
      source
      It returns either a complex selector list,
      or failure.
      Let
      selector
      be the result of
      parsing
      source
      as a

      If this returns failure,
      it’s an
      invalid selector
      return failure.
      If
      selector
      is an
      invalid selector
      for any other reason
      (such as, for example, containing an undeclared namespace prefix),
      return failure.
      Otherwise,
      return
      selector
      17.3.
      Match a Selector Against an Element
      This section defines how to
      match a selector against an element
      APIs using this algorithm must provide a
      selector
      and an
      element
      Callers may optionally provide:
      one or more
      scoping roots
      for resolving the
      :scope
      pseudo-class against.
      This algorithm returns either success or failure.
      For each
      complex selector
      in the given
      selector
      (which is taken to be a
      list of complex selectors
      ),
      match the complex selector against
      element
      as described in the following paragraph.
      If the matching returns success for any complex selector,
      then the algorithm return success; otherwise it returns failure.
      To
      match a complex selector against an element
      process it
      compound selector
      at a time,
      in right-to-left order.
      This process is defined recursively as follows:
      If any simple selectors in the rightmost compound selector
      does not match the element, return failure.
      Otherwise, if there is only one compound selector in the
      complex selector, return success.
      Otherwise, consider all possible elements
      that could be related to this element by the rightmost
      combinator
      If the operation of matching the selector consisting of this selector
      with the rightmost compound selector and rightmost combinator removed
      against any one of these elements returns success, then return success.
      Otherwise, return failure.
      17.4.
      Match a Selector Against a Pseudo-element
      This section defines how to
      match a selector against a pseudo-element
      APIs using this algorithm must provide a
      selector
      and a
      pseudo-element
      They may optionally provide the same things they may optionally provide
      to the algorithm to
      match a selector against an element
      This algorithm returns success or failure.
      For each
      complex selector
      in the given
      selector
      , if both:
      the rightmost
      simple selector
      in the complex selector
      matches
      pseudo-element
      , and
      the result of running
      match a complex selector against an element
      on the remainder of the
      complex selector
      (with just the rightmost simple selector
      of its rightmost complex selector removed),
      pseudo-element
      ’s corresponding element,
      and any optional parameters provided to this algorithm
      returns success,
      then return success.
      Otherwise
      (that is, if this doesn’t happen for any of the complex selectors in
      selector
      ),
      return failure.
      17.5.
      Match a Selector Against a Tree
      This section defines how to
      match a selector against a tree
      APIs using this algorithm must provide a selector,
      and one or more
      root elements
      indicating the
      subtrees
      that will be searched by the selector.
      All of the
      root elements
      must share the same
      root
      or else calling this algorithm is invalid.
      They may optionally provide:
      One or more
      scoping roots
      indicating the selector is
      scoped
      A list of
      pseudo-elements
      that are allowed to show up in the match list.
      If not specified, this defaults to allowing all pseudo-elements.
      Only the
      tree-abiding pseudo-elements
      are really
      handled in any way remotely like this.
      This algorithm returns a (possibly empty) list of elements.
      Start with a list of
      candidate elements
      which are the
      root elements
      and all of their descendant elements,
      sorted in
      shadow-including tree order
      unless otherwise specified.
      If
      scoping root
      were provided,
      then remove from the
      candidate elements
      any elements that are not
      descendants
      of at least one
      scoping root
      Initialize the
      selector match list
      to empty.
      For each
      element
      in the set of
      candidate elements
      If the result of
      match a selector against an element
      for
      element
      and
      selector
      is success,
      add
      element
      to the
      selector match list
      For each possible pseudo-element associated with
      element
      that is one of the pseudo-elements allowed to show up in the match list,
      if the result of
      match a selector against a pseudo-element
      for the pseudo-element and
      selector
      is success,
      add the pseudo-element to the
      selector match list
      The relative position of pseudo-elements
      in
      selector match list
      is undefined.
      There’s not yet a context that exposes this information,
      but we need to decide on something eventually,
      before something
      is
      exposed.
      Appendix A: Guidance on Mapping Source Documents & Data to an Element Tree
      This section is informative.
      The element tree structure described by the DOM is powerful and useful,
      but generic enough to model pretty much any language that describes tree-based data
      (or even graph-based, with a suitable interpretation).
      Some languages, like HTML, already have well-defined procedures
      for producing a DOM object from a resource.
      If a given language does not,
      such a procedure must be defined
      in order for Selectors to apply to documents in that language.
      At minimum,
      the document language must define what maps to the DOM concept of an "element".
      The primary one-to-many relationship between nodes—​parent/child in tree-based structures,
      element/neighbors in graph-based structures—​should be reflected as the child nodes of an element.
      Other features of the element should be mapped
      to something that serves a similar purpose to the same feature in DOM:
      type
      If the elements in the document language have some notion of "type"
      as a basic distinguisher between different groups of elements,
      it should be reflected as the "type" feature.
      If this "type" can be separated into a "basic" name
      and a "namespace" that groups names into higher-level groups,
      the latter should be reflected as the "namespace" feature.
      Otherwise, the element shouldn’t have a "namespace" feature,
      and the entire name should be reflected as the "type" feature.
      id
      If some aspect of the element functions as a unique identifier across the document,
      it should be mapped to the "id" feature.
      Note:
      While HTML only allows an element to have a single ID,
      this should not be taken as a general restriction.
      The important quality of an ID is that each ID should be associated with a single element;
      a single element can validly have multiple IDs.
      classes and attributes
      Aspects of the element that are useful for identifying the element,
      but are not generally unique to elements within a document,
      should be mapped to the "class" or "attribute" features
      depending on if they’re something equivalent to a "label" (a string by itself)
      or a "property" (a name/value pair)
      pseudo-classes and pseudo-elements
      If any elements match any pseudo-classes or have any pseudo-elements,
      that must be explicitly defined.
      Some pseudo-classes are *syntactical*,
      like
      :has()
      and
      :is()
      and thus should always work.
      Need to indicate that somewhere.
      Probably the structural pseudos always work
      whenever the child list is ordered.
      For example,
      JSONSelect
      is a library that uses selectors
      to extract information from JSON documents.
      The "elements" of the JSON document
      are each array, object, boolean, string, number, or null.
      The array and object elements have their contents as children.
      Each element’s type is its JS type name:
      "array", "object", etc.
      Children of an object
      have their key as a class.
      Children of an array match the
      :first-child
      :nth-child()
      , etc pseudo-classes.
      The root object matches
      :root
      It additionally defines
      :val()
      and
      :contains()
      pseudo-classes,
      for matching boolean/number/string elements with a particular value
      or which contain a particular substring.
      This structure is sufficient to allow powerful, compact querying of JSON documents with selectors.
      Appendix B: Obsolete but Required
      -webkit-
      Parsing Quirks for Web Compat
      Tests
      webkit-pseudo-element.html
      (live test)
      (source)
      This appendix is normative.
      Due to legacy Web-compat constraints,
      user agents expecting to parse Web documents must support the following features:
      :-webkit-autofill
      must be treated as a
      legacy selector alias
      of
      :autofill
      All other
      pseudo-elements
      whose names begin with the string “-webkit-”
      (matched
      ASCII case-insensitively
      and that are not functional notations
      must be treated as valid at parse time.
      (That is,
      ::-webkit-asdf
      is valid at parse time,
      but
      ::-webkit-jkl()
      is not.)
      If they’re not otherwise recognized and supported,
      they must be treated as matching nothing, and are
      unknown -webkit- pseudo-elements
      Unknown -webkit- pseudo-elements
      must be serialized in ASCII lowercase.
      What’s this quirk about?
      Selectors have long had a behavior
      where a single unknown/invalid selector
      invalidates the entire selector list
      (rather than just invalidating the one complex selector it finds itself in).
      This is generally considered a legacy mistake by the WG,
      but can’t be fixed at this point,
      as too many stylesheets depend on this behavior,
      intentionally or not.
      One aspect of this is that use of vendor-specific selectors
      invalidates the entire selector in other user agents
      that don’t recognize them,
      and takes the entire style rule down with it.
      This has been used intentionally in the past—​in the severely-not-recommended practice of hiding style rules from some browsers
      by making them invalid in every other browser—​and unintentionally,
      with people styling an element
      and also applying those styles to a vendor-specific pseudo-element
      (such as the various
      input
      -related pseudos some browsers expose),
      not realizing that this hides the entire rule from other browsers.
      In addition to this more general reasoning,
      WebKit-derived user agents,
      such as Safari or Chrome,
      have an additional quirk related to their vendor-prefixed pseudo-elements,
      where any
      ::-webkit-
      -prefixed selectors are considered valid at parse time.
      (This is probably a leftover quirk of an early CSS feature,
      since dropped,
      that intentionally treated all possible pseudo-elements as valid at parse time,
      in anticipation of a feature letting authors define their own pseudo-elements.)
      Similar to other legacy quirks,
      such as those documented in
      [QUIRKS]
      this particular vendor-specific oddity has become common enough
      that other user agents are seeing sites breaking due to them depending on it,
      accidentally or not.
      As such, since the quirk is in practical terms
      required
      to render the modern web correctly,
      specifying it and requiring it for all user agents
      ensures that today’s web pages are more likely to be correctly rendered
      in user agents both current and future.
      As usual with quirks, however,
      webpages intentionally relying on this
      will be met with shaming and derision from members of the CSSWG,
      and all right-thinking web developers.
      Appendix C: Example Privacy-Preserving
      :visited
      Restrictions
      Previous attempts to protect user privacy in
      :visited
      involved
      complex restrictions and behaviors
      to "lie" about whether the link match
      :visited
      or
      :link
      to reduce the chance that a hostile site
      could observe what unrelated sites a user had visited
      while still allowing
      :visited
      to work in all cases
      and help the user know what links they’d already clicked.
      This is ultimately an arms race that can’t be won;
      there are multiple documented ways to still extract a user’s browsing history
      even with these mitigations.
      This section describes an approach first developed and documented at
      that partitions a user’s browsing history information,
      to allow
      :visited
      to only match links
      corresponding to navigations that the site’s origin could have observed on its own.
      With this,
      :visited
      can be treated as a normal pseudo-class,
      without any of the complex mitigations described above,
      as it doesn’t expose any information not already theoretically available to the site,
      while still preserving as much of the
      usefulness
      of
      :visited
      as possible for the user.
      Let
      visited history
      be a
      set
      containing
      tuples
      of three pieces of information:
      a visited
      URL
      an
      origin
      for the site that started a navigation
      site
      for the top-level site containing the frame that started the navigation.
      (This will often be the same as the previous,
      but can differ if the user clicks a link in a iframe, for example.)
      Whenever a navigation is triggered
      from within a page
      —​e.g.,
      from the user clicking a link,
      or a script on the page initiating a navigation—​add an entry to
      visited history
      recording the navigation’s destination URL,
      the origin of the page containing the link or script,
      and the (schemeful) site of the top-level site containing that
      page (which might be the same site as the previous origin).
      Note:
      This allows a site to see
      :visited
      information
      for links that the user has clicked
      from anywhere in that site’s origin.
      In other words, any
      A -> B
      where the site is A.
      Additionally, add an entry to
      visited history
      recording the destination’s URL, the
      destination’s
      origin, and the
      destination’s
      site. Do this only
      for navigations from top-level frames or iframes which are
      same-origin with their top-level frame.
      Note:
      This allows for a site to see
      :visited
      information about its own pages
      (which is already observable by the site)
      regardless of what site initiated the navigation to that page.
      In other words, any
      A -> B
      where the site is B.
      Note:
      Notably, direct navigations triggered by the
      user agent’s
      UI,
      such as typing into the address bar,
      clicking on bookmarks,
      or dragging a link from another program into the page,
      do not
      add a
      visited history
      entry.
      These can, of course,
      still add to the browser’s record of visited sites
      that it uses for other purposes,
      such as suggesting URLs as the user types into the URL bar.
      When determining if a link element should match
      :link
      or
      :visited
      only allow it to match
      :visited
      if
      the link’s destination,
      the origin of the page containing the link,
      and the top-level site containing the link
      match a tuple in
      visited history
      The inclusion of both page origin and top-level site
      prevents several possible privacy attacks,
      such as:
      If history entries were
      only
      keyed by the starting site’s URL,
      a tracking site could be embedded in a hidden iframe on multiple sites
      which triggers a navigation to a unique URL for a user on the first visit,
      and then uses many such links on subsequent visits
      to see which one had been visited,
      effectively becoming a new "third-party cookie"
      identifying the user across the web.
      By keying the history entry with the top-level site,
      this information can’t be shared across different sites.
      If history entires were
      only
      keyed by the top-level site’s URL,
      a hostile iframe,
      perhaps included in a page as part of an advertisement,
      could observe what sites were visited from the top-level site.
      By keying the history entry with the link’s own site,
      the top-level site’s information can’t "leak" into cross-origin iframes.
      18.
      Changes
      18.1.
      Changes since the 11 November 2022 Working Draft
      Significant changes since the
      11 November 2022 Working Draft
      Defined language range as BCP 47 extended language range
      Issue 13646>
      Removed the at-risk status from
      :read-write
      and
      :has()
      Added
      :popover-open
      pseudo-class.
      Issue 8637
      Made
      :has()
      and the selector argument of
      :nth-child()
      :nth-last-child()
      no longer forgiving.
      Issue 7676
      Moved the legacy single-colon pseudo-element syntax into the grammar itself.
      Issue 8122
      Deferred the
      :local-link
      pseudo-class to Level 5.
      Issue 12799
      Deferred the
      :interest-source
      and
      :interest-target
      pseudo-classes to Level 5.
      Issue 12799
      Deferred the
      :blank
      pseudo-class to Level 5.
      Issue 12799
      Deferred the
      grid-structural (column) selectors
      to Level 5.
      Issue 12799
      Deferred the
      time-dimensional pseudo-classes
      to Level 5.
      Issue 12799
      18.2.
      Changes since the 7 May 2022 Working Draft
      Significant changes since the
      7 May 2022 Working Draft
      Added
      :open
      pseudo-class.
      Issue 7319
      Issue 11039
      Disallowed
      pseudo-elements
      from
      :has()
      unless explicitly allowed
      by the pseudo-element’s definition.
      Issue 7463
      Disallowed nesting of
      :has()
      Issue 7344
      Defined matching of
      ::lang("")
      and of elements not tagged with a language.
      Issue 6915
      Untangled the concepts of "scoped" and "relative" selectors completely.
      Issue 6399
      Removed "absolutize a selector" as well,
      and just defined relative selector matching
      in terms of the anchoring element.
      Reverted compound selector limitation on
      :nth-child()
      Issue 3760
      Defined
      :-webkit-autofill
      legacy selector alias
      Issue 7474
      18.3.
      Changes since the 21 November 2018 Working Draft
      Significant changes since the
      21 November 2018 Working Draft
      Removed the Selector profiles, marked
      :has()
      as optional and at-risk instead.
      Issue 3925
      Added
      § 3.6.4 Sub-pseudo-elements
      to define
      sub-pseudo-elements
      and related terminology.
      Added
      :defined
      Issue 2258
      Added
      :modal
      Issue 6965
      Added
      :fullscreen
      and
      :picture-in-picture
      Issue 3796
      Added
      :seeking
      :buffering
      , and
      :stalled
      media playback state pseudo-classes.
      Issue 3821
      Added
      :muted
      and
      :volume-locked
      sound state pseudo-classes.
      Issue 3821
      and
      Issue 3933
      Added
      :autofill
      Issue 5775
      Added
      :user-valid
      Discussion
      Defined
      :is()
      :where()
      :has()
      :nth-child()
      , and
      :nth-last-child()
      to not be themselves invalidated when containing an invalid selector.
      Issue 3264
      Limited selectors in
      :nth-child()
      and
      :nth-last-child()
      to
      compound selectors
      for now.
      Issue 3760
      Clarified case-sensitive string matching by referencing string identity as defined in
      [INFRA]
      Clarified that UA-provided placeholder text still triggers
      :placeholder-shown
      Rewrote
      :focus-visible
      definition for clarity.
      Switched reminder note in the grammar section to normative text
      describing the requirement of whitespace between

      when a

      token is missing.
      18.4.
      Changes since the 2 February 2018 Working Draft
      Significant changes since the
      2 February 2018 Working Draft
      Named the zero-specificity selector to
      :where()
      Issue 2143
      Renamed
      :matches()
      to
      :is()
      Issue 3258
      Redefined
      :empty
      to ignore white-space–only nodes.
      Issue 1967
      Redefined
      :blank
      to represent empty user input, rather than empty elements.
      Issue 1283
      Changed the specificity of
      :is()
      :has()
      , and
      :nth-child()
      to not depend on which selector argument matched.
      Issue 1027
      Dropped the
      :drop()
      pseudo-classes since HTML dropped the related feature.
      Issue 2257
      Added the case-sensitive flag
      to the attribute selector.
      Issue 2101
      Added further guidance on
      :focus-visible
      Added
      Appendix B: Obsolete but Required -webkit- Parsing Quirks for Web Compat
      defining
      ::-webkit-
      pseudo-element parsing quirk.
      Issue 3051
      Rewrote grammar rules about where white space is allowed for clarity.
      (See
      § 16 Grammar
      .)
      18.5.
      Changes since the 2 May 2013 Working Draft
      Significant changes since the
      2 May 2013 Working Draft
      include:
      Added the
      :target-within
      :focus-within
      :focus-visible
      :playing
      , and
      :paused
      pseudo-classes.
      Added a zero-specificity
      :matches()
      -type pseudo-class, with name TBD.
      Replaced subject indicator (
      ) feature with
      :has()
      Replaced the
      :nth-match()
      and
      :nth-last-match()
      selectors
      with
      :nth-child(… of
      selector
      and
      :nth-last-child(… of
      selector
      Changed the
      :active-drop-target
      :valid-drop-target
      :invalid-drop-target
      with
      :drop()
      Sketched out an empty-or-whitespace-only selector for discussion
      (See
      open issue
      .)
      Renamed
      :user-error
      to
      :user-invalid
      (See
      Discussion
      Renamed
      :nth-column()
      :nth-last-column()
      to
      :nth-col()
      :nth-last-col()
      to avoid naming confusion with a potential
      ::column
      pseudo-class.
      Changed the non-functional form of the
      :local-link
      pseudo-class to account for fragment URLs.
      Removed the functional form of the
      :local-link()
      pseudo-class and reference combinator for lack of interest.
      Rewrote selectors grammar using the CSS Value Definition Syntax.
      Split out
      relative selectors
      from
      scoped selectors
      as these are different concepts that can be independently invoked.
      Moved definition of

      microsyntax to CSS Syntax.
      Semantic definition should probably move back here.
      Added new sections:
      § 3.2 Data Model
      Need to define tree for XML.
      § 17 API Hooks
      Note that earlier versions of this section defined a section on
      evaluating a selector
      but that section is no longer present.
      Specifications referencing that section should instead reference
      the algorithm to
      match a selector against a tree
      Removed restriction on combinators within
      :matches()
      and
      :not()
      see
      discussion
      Defined
      specificity
      of a
      selector list
      . (Why?)
      Required quotes around
      :lang()
      values involving an asterisk;
      only language codes which happen to be CSS identifiers can be used unquoted.
      Note:
      The 1 February 2018 draft included an inadvertent commit of unfinished work;
      2 February 2018 has reverted this commit (and fixed some links because why not).
      18.6.
      Changes since the 23 August 2012 Working Draft
      Significant changes since the
      23 August 2012 Working Draft
      include:
      Added
      :placeholder-shown
      pseudo-classes.
      Released some restrictions on
      :matches()
      and
      :not()
      Defined fast and complete Selectors profiles (now called “live” and “snapshot”).
      Improved definition of
      specificity
      to better handle
      :matches()
      Updated grammar.
      Cleaned up definition of

      notation.
      Added definition of
      scope-relative
      selectors, changed
      scope-constrained
      to scope-filtered for less confusion with scope-contained.
      The
      :local-link()
      pseudo-class now ignores trailing slashes.
      18.7.
      Changes since the 29 September 2011 Working Draft
      Significant changes since the
      29 September 2011 Working Draft
      include:
      Added language variant handling per RFC 4647.
      Added scoped selectors.
      Added
      :user-error
      (now called
      :user-invalid
      ).
      Added
      :valid-drop-target
      Changed
      column combinator
      from double slash to double pipe.
      18.8.
      Changes Since Level 3
      Additions since
      Level 3
      Extended
      :not()
      to accept a selector list.
      Added
      :is()
      and
      :where()
      and
      :has()
      Added
      :scope
      Added
      :any-link
      Added
      :focus-within
      , and
      :focus-visible
      Added
      :dir()
      Expanded
      :lang()
      to accept wildcard matching and lists of language codes.
      Expanded
      :nth-child()
      to accept a selector list.
      Merged in input selectors from
      CSS Basic User Interface Module Level 3
      and added back
      :indeterminate
      Added
      :user-invalid
      Added case-insensitive / case-sensitive attribute-value matching flags.
      19.
      Acknowledgements
      The CSS working group would like to thank everyone who contributed
      to the
      previous Selectors
      specifications over the years,
      as those specifications formed the basis for this one.
      In particular, the working group would like to extend special thanks
      to the following for their specific contributions to Selectors Level 4:
      L. David Baron,
      Andrew Fedoniouk,
      Daniel Glazman,
      Ian Hickson,
      Grey Hodge,
      Lachlan Hunt,
      Anne van Kesteren,
      Jason Cranford Teague,
      Lea Verou
      Privacy Considerations
      The
      :visited
      pseudo-class can expose information about which sites a user has previously visited,
      if the UA is not careful to screen from scripting any information that would reveal
      which elements match it.
      The
      :autofill
      pseudo-class can expose whether a user has interacted with this form before;
      however the same information can be derived by observing how quickly the form is filled out.
      Security Considerations
      The
      Privacy Considerations
      could also be considered to affect Security.
      Conformance
      Document conventions
      Conformance requirements are expressed with a combination of
      descriptive assertions and RFC 2119 terminology. The key words “MUST”,
      “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
      “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
      document are to be interpreted as described in RFC 2119.
      However, for readability, these words do not appear in all uppercase
      letters in this specification.
      All of the text of this specification is normative except sections
      explicitly marked as non-normative, examples, and notes.
      [RFC2119]
      Examples in this specification are introduced with the words “for example”
      or are set apart from the normative text with
      class="example"
      like this:
      This is an example of an informative example.
      Informative notes begin with the word “Note” and are set apart from the
      normative text with
      class="note"
      , like this:
      Note, this is an informative note.
      Advisements are normative sections styled to evoke special attention and are
      set apart from other normative text with

      , like
      this:
      UAs MUST provide an accessible alternative.
      Tests
      Tests relating to the content of this specification
      may be documented in “Tests” blocks like this one.
      Any such block is non-normative.
      Conformance classes
      Conformance to this specification
      is defined for three conformance classes:
      style sheet
      CSS
      style sheet
      renderer
      UA
      that interprets the semantics of a style sheet and renders
      documents that use them.
      authoring tool
      UA
      that writes a style sheet.
      A style sheet is conformant to this specification
      if all of its statements that use syntax defined in this module are valid
      according to the generic CSS grammar and the individual grammars of each
      feature defined in this module.
      A renderer is conformant to this specification
      if, in addition to interpreting the style sheet as defined by the
      appropriate specifications, it supports all the features defined
      by this specification by parsing them correctly
      and rendering the document accordingly. However, the inability of a
      UA to correctly render a document due to limitations of the device
      does not make the UA non-conformant. (For example, a UA is not
      required to render color on a monochrome monitor.)
      An authoring tool is conformant to this specification
      if it writes style sheets that are syntactically correct according to the
      generic CSS grammar and the individual grammars of each feature in
      this module, and meet all other conformance requirements of style sheets
      as described in this module.
      Partial implementations
      So that authors can exploit the forward-compatible parsing rules to
      assign fallback values, CSS renderers
      must
      treat as invalid (and
      ignore
      as appropriate
      ) any at-rules, properties, property values, keywords,
      and other syntactic constructs for which they have no usable level of
      support. In particular, user agents
      must not
      selectively
      ignore unsupported component values and honor supported values in a single
      multi-value property declaration: if any value is considered invalid
      (as unsupported values must be), CSS requires that the entire declaration
      be ignored.
      Implementations of Unstable and Proprietary Features
      To avoid clashes with future stable CSS features,
      the CSSWG recommends
      following best practices
      for the implementation of
      unstable
      features and
      proprietary extensions
      to CSS.
      Non-experimental implementations
      Once a specification reaches the Candidate Recommendation stage,
      non-experimental implementations are possible, and implementors should
      release an unprefixed implementation of any CR-level feature they
      can demonstrate to be correctly implemented according to spec.
      To establish and maintain the interoperability of CSS across
      implementations, the CSS Working Group requests that non-experimental
      CSS renderers submit an implementation report (and, if necessary, the
      testcases used for that implementation report) to the W3C before
      releasing an unprefixed implementation of any CSS features. Testcases
      submitted to W3C are subject to review and correction by the CSS
      Working Group.
      Further information on submitting testcases and implementation reports
      can be found from on the CSS Working Group’s website at
      Questions should be directed to the
      public-css-testsuite@w3.org
      mailing list.
      Index
      Terms defined by this specification
      , in § 14.3
      , in § 14.2
      , in § 14.4
      :active
      , in § 9.2
      anchor element
      , in § 3.4
      :any-link
      , in § 8.1

      , in § 16
      attribute selector
      , in § 6

      , in § 16

      , in § 16
      :autofill
      , in § 12.1.4
      :buffering
      , in § 10.2
      :checked
      , in § 12.2.1
      child combinator
      , in § 14.2

      , in § 16
      class selector
      , in § 6.6

      , in § 16
      combinator
      , in § 3.1

      , in § 16

      , in § 16

      , in § 16
      complex selector
      , in § 3.1

      , in § 16

      , in § 16

      , in § 16
      compound selector
      , in § 3.1

      , in § 16
      declared
      , in § 3.8
      :default
      , in § 12.1.5
      :defined
      , in § 5.4
      descendant combinator
      , in § 14.1
      :dir()
      , in § 7.1
      :disabled
      , in § 12.1.1
      document language
      , in § 3.2
      :empty
      , in § 13.2
      :enabled
      , in § 12.1.1
      evaluating a selector
      , in § 18.5
      featureless
      , in § 3.2.1
      :first-child
      , in § 13.3.3
      :first-of-type
      , in § 13.4.3
      :focus
      , in § 9.3
      :focus-visible
      , in § 9.4
      :focus-within
      , in § 9.5

      , in § 16.1
      :fullscreen
      , in § 11.4
      functional pseudo-class
      , in § 3.5
      functional pseudo-element
      , in § 3.6.1
      :has()
      , in § 4.5
      :has-allowed pseudo-element
      , in § 4.5
      host language
      , in § 3.2
      :hover
      , in § 9.1

      , in § 16
      ID selector
      , in § 6.7
      :indeterminate
      , in § 12.2.1
      indicate focus
      , in § 9.4
      input value pseudo-classes
      , in § 12.2.1
      :in-range
      , in § 12.3.2
      :invalid
      , in § 12.3.1
      invalid
      , in § 3.9
      invalid selector
      , in § 3.9
      :is()
      , in § 4.2
      :lang()
      , in § 7.2
      language range
      , in § 7.2
      :last-child
      , in § 13.3.4
      :last-of-type
      , in § 13.4.4

      , in § 16
      legacy selector alias
      , in § 3.10
      :link
      , in § 8.2
      list of complex selectors
      , in § 3.1
      list of compound selectors
      , in § 3.1
      list of selectors
      , in § 3.1
      list of simple selectors
      , in § 3.1
      logical combination pseudo-classes
      , in § 4
      match
      , in § 3.1
      match a complex selector against an element
      , in § 17.3
      match a selector against an element
      , in § 17.3
      match a selector against a pseudo-element
      , in § 17.4
      match a selector against a tree
      , in § 17.5
      :matches()
      , in § 4.2
      :modal
      , in § 11.3
      :muted
      , in § 10.3
      next-sibling combinator
      , in § 14.3
      :not()
      , in § 4.3

      , in § 16
      :nth-child()
      , in § 13.3.1
      :nth-last-child()
      , in § 13.3.2
      :nth-last-of-type()
      , in § 13.4.2
      :nth-of-type()
      , in § 13.4.1
      :only-child
      , in § 13.3.5
      :only-of-type
      , in § 13.4.5
      :open
      , in § 11.1
      :optional
      , in § 12.3.3
      originating element
      , in § 3.6.2
      originating pseudo-element
      , in § 3.6.4
      :out-of-range
      , in § 12.3.2
      parse a relative selector
      , in § 17.2
      parse as a forgiving selector list
      , in § 16.1
      parse a selector
      , in § 17.1
      :paused
      , in § 10.1
      :picture-in-picture
      , in § 11.5
      :placeholder-shown
      , in § 12.1.3
      :playing
      , in § 10.1
      :popover-open
      , in § 11.2
      pseudo-class
      , in § 3.5

      , in § 16

      , in § 16
      pseudo-compound selector
      , in § 3.1
      pseudo-elements
      , in § 3.6

      , in § 16
      :read-only
      , in § 12.1.2
      :read-write
      , in § 12.1.2
      relative
      , in § 3.4

      , in § 16

      , in § 16

      , in § 16
      relative selector
      , in § 3.4
      relative selector anchor elements
      , in § 3.4

      , in § 16
      :required
      , in § 12.3.3
      :root
      , in § 13.1
      :scope
      , in § 8.4
      scope
      , in § 3.3
      scoped selector
      , in § 3.3
      scoping root
      , in § 3.3
      :seeking
      , in § 10.1
      selector
      , in § 3.1

      , in § 16
      selector list
      , in § 3.1

      , in § 16
      simple selector
      , in § 3.1

      , in § 16
      specificity
      , in § 15
      :stalled
      , in § 10.2
      structural pseudo-classes
      , in § 13

      , in § 16
      subject
      , in § 3.1
      subject of a selector
      , in § 3.1
      subject of the selector
      , in § 3.1
      sub-pseudo-element
      , in § 3.6.4
      subsequent-sibling combinator
      , in § 14.4
      :target
      , in § 8.3

      , in § 16
      type selector
      , in § 5.1
      ultimate originating element
      , in § 3.6.4
      :unchecked
      , in § 12.2.1
      universal selector
      , in § 5.2
      unknown -webkit- pseudo-elements
      , in § Unnumbered section
      user action pseudo-class
      , in § 9
      :user-invalid
      , in § 12.3.4
      :user-valid
      , in § 12.3.4
      :valid
      , in § 12.3.1
      :visited
      , in § 8.2
      :volume-locked
      , in § 10.3
      :where()
      , in § 4.4
      White space
      , in § 3.7

      , in § 16
      Terms defined by reference
      [CSS-COLOR-5]
      defines the following terms:
      [CSS-DISPLAY-3]
      defines the following terms:
      display
      [CSS-DISPLAY-4]
      defines the following terms:
      box tree
      display type
      list-item
      visibility
      [CSS-MULTICOL-2]
      defines the following terms:
      ::column
      [CSS-POSITION-4]
      defines the following terms:
      top layer
      [CSS-PSEUDO-4]
      defines the following terms:
      ::after
      ::before
      ::first-letter
      ::first-line
      ::marker
      tree-abiding pseudo-elements
      [CSS-SHADOW-1]
      defines the following terms:
      ::slotted()
      :host
      :host-context()
      flat tree
      [CSS-TEXT-4]
      defines the following terms:
      content language
      document white space characters
      [CSS-VALUES-4]
      defines the following terms:


      identifier
      [CSS-WRITING-MODES-3]
      defines the following terms:
      direction
      [CSS21]
      defines the following terms:
      :before
      [CSS3NAMESPACE]
      defines the following terms:
      @namespace
      CSS qualified name
      default namespace
      [CSS3SYN]
      defines the following terms:






      parse
      parse a list
      [CSSOM-1]
      defines the following terms:
      getComputedStyle(elt)
      [DOM]
      defines the following terms:
      DocumentFragment
      descendant
      document element
      inclusive sibling
      parentNode
      quirks mode
      root
      shadow host
      shadow tree
      shadow-including tree order
      tree
      [FULLSCREEN]
      defines the following terms:
      requestFullscreen()
      [HTML]
      defines the following terms:
      :user-invalid
      area
      audio
      button
      checked
      custom element
      details
      dialog
      div
      effective media volume
      element definition
      em
      h1
      href
      html
      img
      indeterminate
      input
      label
      li
      media data
      media element stall timeout
      meta
      muted
      object
      ol
      option
      origin
      placeholder
      popover
      popover visibility state
      pre
      progress
      select
      selected
      showModal()
      site
      span
      textarea
      video
      [INFRA]
      defines the following terms:
      ASCII case-insensitive
      identical to
      set
      tuple
      [MATHML-CORE]
      defines the following terms:
      math
      [SELECT]
      defines the following terms:
      [SELECTORS-5]
      defines the following terms:
      :blank
      :interest-source
      :interest-target
      :local-link
      :nth-col()
      :nth-last-col()
      column combinator
      [URL]
      defines the following terms:
      fragment
      URL
      References
      Normative References
      [BCP47]
      A. Phillips, Ed.; M. Davis, Ed..
      Tags for Identifying Languages
      . September 2009. Best Current Practice. URL:
      [CSS-DISPLAY-4]
      Elika Etemad; Tab Atkins Jr..
      CSS Display Module Level 4
      . URL:
      [CSS-MULTICOL-2]
      Florian Rivoal; Rachel Andrew.
      CSS Multi-column Layout Module Level 2
      . URL:
      [CSS-POSITION-4]
      Elika Etemad; Tab Atkins Jr..
      CSS Positioned Layout Module Level 4
      . URL:
      [CSS-PSEUDO-4]
      Elika Etemad; Alan Stearns.
      CSS Pseudo-Elements Module Level 4
      . URL:
      [CSS-SHADOW-1]
      CSS Shadow Module Level 1
      . Editor's Draft. URL:
      [CSS-TEXT-4]
      Elika Etemad; et al.
      CSS Text Module Level 4
      . URL:
      [CSS-VALUES-4]
      Tab Atkins Jr.; Elika Etemad.
      CSS Values and Units Module Level 4
      . URL:
      [CSS-WRITING-MODES-3]
      Elika Etemad; Koji Ishii.
      CSS Writing Modes Level 3
      . URL:
      [CSS21]
      Bert Bos; et al.
      Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
      . URL:
      [CSS3NAMESPACE]
      Elika Etemad.
      CSS Namespaces Module Level 3
      . URL:
      [CSS3SYN]
      Tab Atkins Jr.; Simon Sapin.
      CSS Syntax Module Level 3
      . URL:
      [DOM]
      Anne van Kesteren.
      DOM Standard
      . Living Standard. URL:
      [HTML]
      Anne van Kesteren; et al.
      HTML Standard
      . Living Standard. URL:
      [INFRA]
      Anne van Kesteren; Domenic Denicola.
      Infra Standard
      . Living Standard. URL:
      [RFC2119]
      S. Bradner.
      Key words for use in RFCs to Indicate Requirement Levels
      . March 1997. Best Current Practice. URL:
      [RFC4647]
      A. Phillips, Ed.; M. Davis, Ed..
      Matching of Language Tags
      . September 2006. Best Current Practice. URL:
      [SELECT]
      Tantek Çelik; et al.
      Selectors Level 3
      . URL:
      [SELECTORS-5]
      Elika Etemad; Tab Atkins Jr..
      Selectors Level 5
      . URL:
      [URL]
      Anne van Kesteren.
      URL Standard
      . Living Standard. URL:
      Non-Normative References
      [CSS-COLOR-5]
      Chris Lilley; Una Kravets; Lea Verou.
      CSS Color Module Level 5
      . URL:
      [CSS-DISPLAY-3]
      Elika Etemad; Tab Atkins Jr..
      CSS Display Module Level 3
      . URL:
      [CSS3UI]
      Tantek Çelik; Florian Rivoal.
      CSS Basic User Interface Module Level 3 (CSS3 UI)
      . URL:
      [CSSOM-1]
      Daniel Glazman; Emilio Cobos Álvarez.
      CSS Object Model (CSSOM)
      . URL:
      [CSSSTYLEATTR]
      Tantek Çelik; Elika Etemad.
      CSS Style Attributes
      . URL:
      [FULLSCREEN]
      Philip Jägenstedt.
      Fullscreen API Standard
      . Living Standard. URL:
      [HTML5]
      Ian Hickson; et al.
      HTML5
      . 27 March 2018. REC. URL:
      [ITS20]
      David Filip; et al.
      Internationalization Tag Set (ITS) Version 2.0
      . 29 October 2013. REC. URL:
      [MATHML]
      Patrick D F Ion; Robert R Miner.
      Mathematical Markup Language (MathML™) 1.01 Specification
      . 7 March 2023. REC. URL:
      [MATHML-CORE]
      David Carlisle; Frédéric Wang.
      MathML Core
      . URL:
      [PICTURE-IN-PICTURE]
      Francois Beaufort.
      Picture-in-Picture
      . URL:
      [QUIRKS]
      Simon Pieters.
      Quirks Mode Standard
      . Living Standard. URL:
      [SVG11]
      Erik Dahlström; et al.
      Scalable Vector Graphics (SVG) 1.1 (Second Edition)
      . 16 August 2011. REC. URL:
      [XFORMS11]
      John Boyer.
      XForms 1.1
      . 20 October 2009. REC. URL:
      [XML-NAMES]
      Tim Bray; et al.
      Namespaces in XML 1.0 (Third Edition)
      . 8 December 2009. REC. URL:
      [XML10]
      Tim Bray; et al.
      Extensible Markup Language (XML) 1.0 (Fifth Edition)
      . 26 November 2008. REC. URL:
      Issues Index
      Add comma-separated syntax for
      multiple-value matching
      e.g. [rel ~= next, prev, up, first, last]
      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)
      Are these still necessary now that we have more rigorous definitions for
      match
      and
      invalid selector
      Nouns are a lot easier to coordinate across specification than predicates,
      and details like the exact order of elements returned from
      querySelector
      seem to make more sense being defined in the DOM specification than in Selectors.
      Only the
      tree-abiding pseudo-elements
      are really
      handled in any way remotely like this.
      The relative position of pseudo-elements
      in
      selector match list
      is undefined.
      There’s not yet a context that exposes this information,
      but we need to decide on something eventually,
      before something
      is
      exposed.
      Some pseudo-classes are *syntactical*,
      like
      :has()
      and
      :is()
      and thus should always work.
      Need to indicate that somewhere.
      Probably the structural pseudos always work
      whenever the child list is ordered.
      Semantic definition should probably move back here.
      Need to define tree for XML.
      MDN
      :active
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      4+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Adjacent_sibling_combinator
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :any-link
      In all current engines.
      Firefox
      50+
      Safari
      9+
      Chrome
      65+
      Opera
      Edge
      79+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      9+
      Chrome for Android
      Android WebView
      65+
      Samsung Internet
      Opera Mobile
      MDN
      Attribute_selectors
      In all current engines.
      Firefox
      1+
      Safari
      3+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      1+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      MDN
      :blank
      In no current engines.
      Firefox
      None
      Safari
      None
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :checked
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      4+
      iOS Safari
      Chrome for Android
      18+
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Child_combinator
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      4+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Class_selectors
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Column_combinator
      In no current engines.
      Firefox
      None
      Safari
      None
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :default
      In all current engines.
      Firefox
      4+
      Safari
      5+
      Chrome
      10+
      Opera
      10+
      Edge
      79+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      5+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Descendant_combinator
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :dir
      Firefox
      49+
      Safari
      16.4+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :disabled
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      :enabled
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :empty
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :first-child
      In all current engines.
      Firefox
      3+
      Safari
      3.1+
      Chrome
      4+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      4+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :first-of-type
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :focus-visible
      In all current engines.
      Firefox
      85+
      Safari
      15.4+
      Chrome
      86+
      Opera
      Edge
      86+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :focus-within
      In all current engines.
      Firefox
      52+
      Safari
      10.1+
      Chrome
      60+
      Opera
      Edge
      79+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :focus
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      7+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      8+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :future
      In only one current engine.
      Firefox
      None
      Safari
      7+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      General_sibling_combinator
      In all current engines.
      Firefox
      1+
      Safari
      3+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      1+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      MDN
      :has
      In all current engines.
      Firefox
      🔰 103+
      Safari
      15.4+
      Chrome
      105+
      Opera
      Edge
      105+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :hover
      In all current engines.
      Firefox
      1+
      Safari
      2+
      Chrome
      1+
      Opera
      4+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      4+
      Firefox for Android
      iOS Safari
      1+
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      ID_selectors
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :in-range
      In all current engines.
      Firefox
      29+
      Safari
      5.1+
      Chrome
      10+
      Opera
      11+
      Edge
      79+
      Edge (Legacy)
      13+
      IE
      None
      Firefox for Android
      16+
      iOS Safari
      Chrome for Android
      Android WebView
      2.2+
      Samsung Internet
      1.0+
      Opera Mobile
      11+
      MDN
      :indeterminate
      In all current engines.
      Firefox
      2+
      Safari
      3+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      10+
      Firefox for Android
      iOS Safari
      1+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :invalid
      In all current engines.
      Firefox
      4+
      Safari
      5+
      Chrome
      10+
      Opera
      10+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      10+
      Firefox for Android
      iOS Safari
      5+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      :valid
      In all current engines.
      Firefox
      4+
      Safari
      5+
      Chrome
      10+
      Opera
      10+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      10+
      Firefox for Android
      iOS Safari
      5+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :is
      In all current engines.
      Firefox
      78+
      Safari
      14+
      Chrome
      88+
      Opera
      Edge
      88+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      14+
      Chrome for Android
      Android WebView
      88+
      Samsung Internet
      15.0+
      Opera Mobile
      MDN
      :lang
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      8+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      8+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :last-child
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :last-of-type
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :link
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      3.2+
      Chrome for Android
      Android WebView
      1.5+
      Samsung Internet
      Opera Mobile
      :visited
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      4+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Selector_list
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :modal
      In all current engines.
      Firefox
      103+
      Safari
      15.6+
      Chrome
      105+
      Opera
      Edge
      105+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :not
      In all current engines.
      Firefox
      1+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :nth-child
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :nth-last-child
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      4+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :nth-last-of-type
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      4+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :nth-of-type
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :only-child
      In all current engines.
      Firefox
      1.5+
      Safari
      3.1+
      Chrome
      2+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :only-of-type
      In all current engines.
      Firefox
      3.5+
      Safari
      3.1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :optional
      In all current engines.
      Firefox
      4+
      Safari
      5+
      Chrome
      10+
      Opera
      10+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      10+
      Firefox for Android
      iOS Safari
      5+
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      :required
      In all current engines.
      Firefox
      4+
      Safari
      5+
      Chrome
      10+
      Opera
      10+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      10+
      Firefox for Android
      iOS Safari
      5+
      Chrome for Android
      Android WebView
      4.4.3+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :out-of-range
      In all current engines.
      Firefox
      29+
      Safari
      5.1+
      Chrome
      10+
      Opera
      11+
      Edge
      79+
      Edge (Legacy)
      13+
      IE
      None
      Firefox for Android
      16+
      iOS Safari
      Chrome for Android
      Android WebView
      2.2+
      Samsung Internet
      Opera Mobile
      11+
      MDN
      :past
      In only one current engine.
      Firefox
      None
      Safari
      7+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :paused
      In only one current engine.
      Firefox
      None
      Safari
      15.4+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :picture-in-picture
      In only one current engine.
      Firefox
      None
      Safari
      None
      Chrome
      110+
      Opera
      Edge
      110+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :placeholder-shown
      In all current engines.
      Firefox
      51+
      Safari
      9+
      Chrome
      47+
      Opera
      Edge
      79+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :playing
      In only one current engine.
      Firefox
      None
      Safari
      15.4+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :read-only
      In all current engines.
      Firefox
      78+
      Safari
      4+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      13+
      IE
      None
      Firefox for Android
      None
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      :read-write
      In all current engines.
      Firefox
      78+
      Safari
      4+
      Chrome
      1+
      Opera
      9+
      Edge
      79+
      Edge (Legacy)
      13+
      IE
      None
      Firefox for Android
      None
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :root
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      MDN
      :scope
      In all current engines.
      Firefox
      32+
      Safari
      7+
      Chrome
      27+
      Opera
      Edge
      79+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :target-within
      In no current engines.
      Firefox
      None
      Safari
      None
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :target
      In all current engines.
      Firefox
      1+
      Safari
      1.3+
      Chrome
      1+
      Opera
      9.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      9+
      Firefox for Android
      iOS Safari
      2+
      Chrome for Android
      Android WebView
      2+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Type_selectors
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      3+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      Universal_selectors
      In all current engines.
      Firefox
      1+
      Safari
      1+
      Chrome
      1+
      Opera
      3.5+
      Edge
      79+
      Edge (Legacy)
      12+
      IE
      7+
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      37+
      Samsung Internet
      Opera Mobile
      10.1+
      MDN
      :user-invalid
      Firefox
      88+
      Safari
      16.5+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :user-valid
      Firefox
      88+
      Safari
      16.5+
      Chrome
      None
      Opera
      Edge
      None
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile
      MDN
      :where
      In all current engines.
      Firefox
      78+
      Safari
      14+
      Chrome
      88+
      Opera
      Edge
      88+
      Edge (Legacy)
      IE
      None
      Firefox for Android
      iOS Safari
      Chrome for Android
      Android WebView
      Samsung Internet
      Opera Mobile