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

[@scope] Support implicit scoping roots #37926

Merged
merged 1 commit into from
Jan 16, 2023

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 13, 2023

This CL makes it possible to specify a @scope rule without any
prelude, scoping the rules implicitly to the parent of the owner node.

This is implemented by storing a StyleSheetContents in each StyleScope,
and treating each owner-parent-node of the StyleSheetContents as a
scoping root.

The following likely doesn't work, and is postponed for future CLs:

  • Constructed stylesheets
  • An owner node whose parent node is a ShadowRoot

w3c/csswg-drafts#7349

Bug: 1379844
Change-Id: Icbfae88636662e9a16dd11f9c7a371c997447f60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4161741
Reviewed-by: Rune Lillesveen <[email protected]>
Commit-Queue: Anders Hartvoll Ruud <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1093015}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

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

The review process for this patch is being conducted in the Chromium project.

This CL makes it possible to specify a @scope rule without any
prelude, scoping the rules implicitly to the parent of the owner node.

This is implemented by storing a StyleSheetContents in each StyleScope,
and treating each owner-parent-node of the StyleSheetContents as a
scoping root.

The following likely doesn't work, and is postponed for future CLs:

 - Constructed stylesheets
 - An owner node whose parent node is a ShadowRoot

w3c/csswg-drafts#7349

Bug: 1379844
Change-Id: Icbfae88636662e9a16dd11f9c7a371c997447f60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4161741
Reviewed-by: Rune Lillesveen <[email protected]>
Commit-Queue: Anders Hartvoll Ruud <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1093015}
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 88acd4d into master Jan 16, 2023
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-4161741 branch January 16, 2023 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants