Closed Bug 1939158 Opened 2 months ago Closed 1 month ago

[wpt-sync] Sync PR 49845 - [layout] Fix dirty bits for container queries.

Categories

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

task

Tracking

()

RESOLVED FIXED
136 Branch
Tracking Status
firefox136 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Ian Kilpatrick <ikilpatrick@chromium.org> wrote:

[layout] Fix dirty bits for container queries.

container-queries mean that we can invalidate layout within layout.

The logic within MarkParentForSpannerOrOutOfFlowPositionedChange
basically wants to invalidate the parents container chain, however it
wasn't quite doing that.

Instead it was invaliding everything between itself, and its
containing block.

This can differ when we have something like a position:absolute. E.g.
previously we invalidated everything, now we invalidate:

ICB *
html
abspos *
parent *
fixedpos

skipping the "html" element.

This caused the html element to have dirty bits set, even though it
had the correct layout.

Fixed: 385317081
Change-Id: I6621104ea636533f2328a7ca1eb18ff2d895c8b7

Reviewed-on: https://chromium-review.googlesource.com/6120747
WPT-Export-Revision: 935f80c472238b4cc9eb38ce22b91707b1322d58

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7671514ca55c [wpt PR 49845] - [layout] Fix dirty bits for container queries., a=testonly
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
You need to log in before you can comment on or make changes to this bug.