Change `&` behaviour inside `@scope` block as per spec resolution
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: dshin, Assigned: dshin)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, Whiteboard: [at-scope-m2], [wptsync upstream])
Attachments
(3 files)
Currently & behaves as if copy and pasting the scope-start-selector.
As per discussion logged in See Also, this is probably going to change:
- Current suggested resolution is
:where(:scope), like the implicitly inserted:scope. - There's going to be another discussion in a week's time to discuss alternatives.
Explainer here
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
•
|
||
Resolution was made to keep the suggested change, so will be working on this.
| Assignee | ||
Comment 2•1 year ago
|
||
... Rather, just use the implicit scope selector, which is effectively the same
thing. This is done as per the recent CSSWG resolution [1].
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
This is as per the CSSWG resolution [1].
- scope-invalidation.html: Adjust for
&no longer inheriting scope start
selector's specificity. - scope-specificity.html: Now equate
@scope(#main) { & .b {} }with
:where(#main) .bin terms of specificity. - scope-nesting.html:
test_nest_scope_end: Now behaves identically to
test_nest_scope_end_implicit_scopetest_inner_nest: Now behaves identically to
test_parent_in_pseudo_scopetest_parent_pseudo_in_nested_scope_end: Removed; there's no equivalence
with implicit:scopetest_insert_ampersand_rule_within_scope: Insert the selector using &
before and after the selector using implicit scope selector, since
order of apperance matters.
Comment 6•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ba63941d4041
https://hg.mozilla.org/mozilla-central/rev/b7593b87da93
Updated•1 year ago
|
| Assignee | ||
Comment 7•1 year ago
|
||
Comment 9•1 year ago
|
||
| bugherder | ||
Comment 10•1 year ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
| Assignee | ||
Comment 11•1 year ago
|
||
(For future reference, this progressed WPT pull request here)
Comment 13•1 year ago
|
||
MDN docs changes for this bug can be tracked here: https://github.com/mdn/content/issues/40481
Description
•