Closed Bug 1924480 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 48597 - [@container] Correctly match snapped on container-type changes

Categories

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

task

Tracking

()

RESOLVED FIXED
133 Branch
Tracking Status
firefox133 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

[@container] Correctly match snapped on container-type changes

Unlike for stuck queries, the snapshot client for snapped queries may
outlive a ContainerQueryEvaluator. If a container-type:scroll-state
which is snapped changes its container-type to 'none' and then back
again we may have a snapped state snapshot that does not need an update
when we re-create the ContainerQueryEvaluator.

Make sure the ContainerQueryEvaluator initializes the ContainerValues
with the snapshot state for snapped queries.

Added a test for the stuck feature to verify that works.

Bug: 40279568
Change-Id: I7ced76e4004e9ab7338c6b75b61fe88215438ff7
Reviewed-on: https://chromium-review.googlesource.com/5926649
WPT-Export-Revision: 64f73ddad71600b6e6b5dc5c172126d7041ab32e

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
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 2 tests and 1 subtests

Status Summary

Firefox

OK : 2
FAIL: 5

Chrome

OK : 2
PASS: 4
FAIL: 1

Safari

OK : 2
FAIL: 5

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/29cc4d9765c4 [wpt PR 48597] - [@container] Correctly match snapped on container-type changes, a=testonly https://hg.mozilla.org/integration/autoland/rev/a5c66783b428 [wpt PR 48597] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in before you can comment on or make changes to this bug.