-
Notifications
You must be signed in to change notification settings - Fork 23k
docs(Fx142): css ampersand in at-scope content and :scope
#40814
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
Conversation
|
Preview URLs Flaws (4)URL:
(comment last updated: 2025-08-28 09:19:54) |
|
I can take up the review for this |
dipikabh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks for capturing the changes in the specificity behavior.
I've added a few rephrasing suggestions.
Co-authored-by: Dipika Bhattacharya <[email protected]>
Co-authored-by: Dipika Bhattacharya <[email protected]>
|
Thanks for the review! @dipikabh do you want to have another look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much better after the cleanup, thanks!
Co-authored-by: Dipika Bhattacharya <[email protected]>
|
Thanks, Dipika! Do you want to have another look? |
|
Looks really good, thanks a lot @bsmth! |
Great, thanks a lot! |
Description
Using
&inside@scopechanges according to spec updates (and relation to:scope).This makes
& &redundant as far as I can see. The explainer has good context and I hope I've conveyed that in these changes.Explainer: https://css.oddbird.net/scope/parent-selector/
Bugs
&behaviour inside@scopeblock as per spec resolutionAdditional details
&behaviour inside@scopeblock as per spec resolution #40481