Closed Bug 1839866 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 40695 - [@scope] Support limits for implicit scopes

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
117 Branch
Tracking Flags:
Tracking Status
firefox117 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

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

[@scope] Support limits for implicit scopes

This adds support for specifying scoping limits [1] for @scope rules
with no \<scope-start> selector.

In other words, the following is now allowed.

@scope to (.limit) { ... }

[1] https://drafts.csswg.org/css-cascade-6/#scoping-limit

Fixed: 1456331
Change-Id: Ia974a79ccc830570b878dc354a90d3d39b7ea9e1
Reviewed-on: https://chromium-review.googlesource.com/4628212
WPT-Export-Revision: b0f2b646a72af10474ec50c8a4b124c34fdc2178

PR 40695 applied with additional changes from upstream: 020b50e83788e69b99c0de741a2e782e1cb225a6
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Test result changes from PR not available.
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/637c468c19f2 [wpt PR 40695] - [@scope] Support limits for implicit scopes, a=testonly https://hg.mozilla.org/integration/autoland/rev/345371320afc [wpt PR 40695] - Update wpt metadata, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/637c468c19f2
https://hg.mozilla.org/mozilla-central/rev/345371320afc

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