2026124 - Support @import scope() (was: New wpt failures in /css/css-cascade/ [scope-import-implicit.html, scope-import-inner-scope.html, scope-import-multiple.html, and 4 others])

Status: NEW

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Syncing wpt PR 58709 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

• /css/css-cascade/scope-import-implicit.html [wpt.fyi]
  • Scope-imported rule applies within implicit scope: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-inner-scope.html [wpt.fyi]
  • @scope within scope-imported stylesheet matches: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-multiple.html [wpt.fyi]
  • A stylesheet may be imported multiple times, and scoped differently: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-parent-pseudo.html [wpt.fyi]
  • The & selector matches the scoping root: FAIL (Chrome: PASS, Safari: FAIL)
  • The & selector behaves like :scope: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-scope-end.html [wpt.fyi]
  • Scope-imported rule applies within scope, above limit: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-scope-pseudo.html [wpt.fyi]
  • The :scope pseudo-class works in imported stylesheets: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-cascade/scope-import-scope-start.html [wpt.fyi]
  • Scope-imported rule applies within scope: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 2025863 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.