[wpt-sync] Sync PR 48597 - [@container] Correctly match snapped on container-type changes
Categories
(Core :: CSS Parsing and Computation, task, P4)
Tracking
()
| 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
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
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
- /css/css-conditional/container-queries/scroll-state-snapped-container-type-change.html [wpt.fyi]
- Check scroll-state(snapped) initially matching:
FAIL(Chrome:PASS, Safari:FAIL) - Check scroll-state(snapped) not matching when scroll-snap-align is removed:
FAIL(Chrome:PASS, Safari:FAIL) - Check scroll-state(snapped) not matching when scroll-snap-type is removed:
FAIL(Chrome:PASS, Safari:FAIL) - Check scroll-state(snapped) not matching when container-type is removed:
FAIL(Chrome:FAIL, Safari:FAIL)
- Check scroll-state(snapped) initially matching:
- /css/css-conditional/container-queries/scroll-state-stuck-container-type-change.html [wpt.fyi]
- Check that scroll-state(stuck: bottom) evaluation changes with container-type changes:
FAIL(Chrome:PASS, Safari:FAIL)
- Check that scroll-state(stuck: bottom) evaluation changes with container-type changes:
Comment 4•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/29cc4d9765c4
https://hg.mozilla.org/mozilla-central/rev/a5c66783b428
Description
•