[go: nahoru, domu]

Skip to content
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.

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

[css-cascade-6] Disallow pseudo-elements in @scope prelude #8461

Merged
merged 3 commits into from
Feb 17, 2023
Merged
Changes from all commits
Commits
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
6 changes: 6 additions & 0 deletions css-cascade-6/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -476,6 +476,9 @@ Scoping Styles: the ''@scope'' rule</h4>
are [=scoped selectors|scoped by=]
the selectors of the outer one.

[=Pseudo-elements=] cannot be [=scoping roots=] or [=scoping limits=];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this move up into 2.5 Scoped Styles where <scope-start> and <scope-end> are defined? Merging as-is, but might want to come back and move this, so making note of it…

they are invalid both within <<scope-start>> and <<scope-end>>.

<h4 id="scope-combinator">
Scoped Descendant Combinator</h4>

Expand Down Expand Up @@ -553,6 +556,9 @@ Changes since the 21 December 2021 First Public Working Draft</h3>
Significant changes since the
<a href="https://www.w3.org/TR/2021/WD-css-cascade-6-20211221/">21 December 2021 First Public Working Draft</a> include:

* Disallowed [=pseudo-elements=] in the ''@scope'' prelude.
(<a href="https://github.com/w3c/csswg-drafts/issues/7382">Issue 7382</a>)

* Removed selector scoping notation.
(<a href="https://github.com/w3c/csswg-drafts/issues/7709">Issue 7709</a>)

Expand Down