Skip to content

[css-cascade-6] Specificity of Implicitly-Added :scope in Scoped Rules #452

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

Jump to bottom
Closed
chromium-helper opened this issue Jun 11, 2024 · 1 comment
Closed

[css-cascade-6] Specificity of Implicitly-Added :scope in Scoped Rules #452

chromium-helper opened this issue Jun 11, 2024 · 1 comment
Labels
css-cascade-6

Comments

@chromium-helper
Copy link
Owner

CSSWG added the following resolution(s):

  • RESOLVED: explicitly state in specs that when an ampersand doesn't actually have a parent rule to draw from then its specificity is zero

in w3c/csswg-drafts#10196 (comment)
@chromium-helper
Copy link
Owner Author

I have filed issues.chromium.org/346559511

That is all that can be done here, closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
css-cascade-6
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chromium-helper