Skip to content

[css-nesting-1] Fix character reference errors #12988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 22, 2025
Merged

[css-nesting-1] Fix character reference errors #12988

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions css-nesting-1/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,10 +327,10 @@ Syntax {#syntax}
as nesting is not a syntax transformation,
but rather matches on the actual elements the parent selector matches.

It is also true that the selector ''&Bar'' is invalid in CSS in the first place,
It is also true that the selector ''&Bar'' is invalid in CSS in the first place,
as the ''Bar'' part is a type selector,
which must come first in the compound selector.
(That is, it must be written as ''Bar&''.)
(That is, it must be written as ''Bar&''.)
So, luckily, there is no overlap between CSS Nesting
and the preprocessor syntax.
</div>
Expand Down Expand Up @@ -1091,10 +1091,10 @@ Nesting Selector: the ''&'' selector {#nest-selector}

While the position of a [=nesting selector=] in a [=compound selector=]
does not make a difference in its behavior
(that is, ''&.foo'' and ''.foo&'' match the same elements),
(that is, ''&amp;.foo'' and ''.foo&amp;'' match the same elements),
the existing rule that a [=type selector=], if present, must be first in the [=compound selector=]
continues to apply
(that is, ''&div'' is illegal, and must be written ''div&'' instead).
(that is, ''&amp;div'' is illegal, and must be written ''div&amp;'' instead).


<!-- Big Text: Nested Decl
Expand Down Expand Up @@ -1350,7 +1350,7 @@ Significant changes since the

* Clarified that the [=nesting selector=] is allowed to match featureless elements.

* Switched ''&div'' back to being invalid;
* Switched ''&amp;div'' back to being invalid;
now that Syntax does "infinite lookahead",
we no longer need to allow it.
Plus, doing so avoids a clash with preprocessors.
Expand Down