Closed Bug 1818188 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 38644 - [@scope] Make '&' in <scope-end> resolve to <scope-start>

Categories

(Core :: CSS Parsing and Computation, task, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
113 Branch
Tracking Flags:
Tracking Status
firefox113 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 38644 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/38644
Details from upstream follow.

Anders Hartvoll Ruud <andruud@chromium.org> wrote:

[@scope] Make '&' in <scope-end> resolve to <scope-start>

Instead of storing the \<scope-start> (i.e. From()) as a CSSSelectorList,
store an empty StyleRule with that same list of selectors.

This allows us to pretend that \<scope-start> is the ancestor rule
for nesting purposes when matching \<scope-end>, as required by spec.

The nesting selector (&) needs to work other places too, but that is
for future CLs to handle.

https://drafts.csswg.org/css-nesting-1/#nesting-at-scope

Bug: 1280240
Change-Id: I52bed7537a6892746bbf638407839abbd11ba96f
Reviewed-on: https://chromium-review.googlesource.com/4274727
WPT-Export-Revision: 9a7f1b064600799bdbf47a2bcab09d53c791396d

PR 38644 applied with additional changes from upstream: 2051d6fcc2366ec9c26e5297a1bf400231428f00
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/df022da2430d [wpt PR 38644] - [@scope] Make '&' in <scope-end> resolve to <scope-start>, a=testonly https://hg.mozilla.org/integration/autoland/rev/cb23a8708690 [wpt PR 38644] - Update wpt metadata, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/df022da2430d
https://hg.mozilla.org/mozilla-central/rev/cb23a8708690

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox113: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in before you can comment on or make changes to this bug.