Skip to content

[css-cascade-6] Add implicit scopes #8463

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
mirisuzanne merged 3 commits into from
Feb 17, 2023
Merged

[css-cascade-6] Add implicit scopes #8463

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bd711bf
[css-cascade-6] Add implicit scopes
andruud Feb 17, 2023
7ca4ee1
Merge branch 'main' into issue_6606
mirisuzanne Feb 17, 2023
4ae7dfd
Allow lower bounds when root is implicit
mirisuzanne Feb 17, 2023
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
Prev Previous commit
Next Next commit
Merge branch 'main' into issue_6606
  • Loading branch information
@mirisuzanne
mirisuzanne authored Feb 17, 2023
commit 7ca4ee1ed092f753265eca0bea8600488e36a005
12 changes: 9 additions & 3 deletions css-cascade-6/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,9 +254,6 @@ Scoped Styles</h2>

[=Scopes=] are described in CSS using the ''@scope'' rule.

[=Pseudo-elements=] cannot be [=scoping roots=] or [=scoping limits=];
they are invalid both within <<scope-start>> and <<scope-end>>.

Note: In contrast to [[CSS-SCOPING-1#shadow-dom|Shadow Encapsulation]],
which describes a persistent one-to-one relationship in the DOM
between a [=shadow host=] and its nested [=shadow tree=],
Expand Down Expand Up @@ -378,6 +375,9 @@ Scoping Styles: the ''@scope'' rule</h4>
using the [=scoping root=] as the '':scope'' element, then
* Set those elements as the [=scoping limits=].

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

@mirisuzanne mirisuzanne Feb 17, 2023

Choose a reason for hiding this comment

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

After moving this above in the previous PR, I moved it back down! 😅

Copy link
Member Author

@andruud andruud Feb 17, 2023

Choose a reason for hiding this comment

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

:-)

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

A ''@scope'' rule which does not specify a <<scope-start>>
produces a single <dfn>implicit scope</dfn> as follows:

Expand Down Expand Up @@ -597,6 +597,12 @@ Changes since the 21 December 2021 First Public Working Draft</h3>
* Added [=implicit scopes=].
(<a href="https://github.com/w3c/csswg-drafts/issues/6606">Issue 6606</a>)

* 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>)

* [=Scoping limit=] elements are excluded from the resulting [=scope=].
(<a href="https://github.com/w3c/csswg-drafts/issues/6577">Issue 6577</a>)

Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.