Closed Bug 1802801 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 37159 - view-transitions: Add test for style query outside transitions.

Categories

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

task

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox109 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Khushal Sagar <khushalsagar@chromium.org> wrote:

view-transitions: Add test for style query outside transitions.

The selector matching code in style cascade assumes that only-child
rules are only matched when there is an active transition. Add a test
which validates this assumption.

R=vmpstr@chromium.org

Bug: 1393279
Change-Id: Ib2d433ad442a4da0d1b340514538fa1a058478eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4054366
Auto-Submit: Khushal Sagar \<khushalsagar@chromium.org>
Reviewed-by: Vladimir Levin \<vmpstr@chromium.org>
Commit-Queue: Khushal Sagar \<khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1076005}

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
PASS: 1

Chrome

OK : 1
PASS: 1

Safari

OK : 1
PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b80de8011f4e [wpt PR 37159] - view-transitions: Add test for style query outside transitions., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in before you can comment on or make changes to this bug.