Closed Bug 1753966 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 32722 - [@container] Out-of-flow replaced not containers in legacy

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

[@container] Out-of-flow replaced not containers in legacy

Out-of-flow positioned replaced elements take the legacy path for layout
if the container for positioning is a legacy object. That is the case
for LayoutView, which is a legacy object but does not otherwise force
legacy layout objects.

Make sure we either don't skip style recalc for such elements, or resume
recalc during AttachLayoutTree() to not leave anything incomplete after
a lifecycle update.

Bug: 1289850
Change-Id: I59a7043eaf073fbf031ca90164788cd5b60f50eb
Reviewed-on: https://chromium-review.googlesource.com/3439924
WPT-Export-Revision: 05ecec9eebe91e6766c2f0f6b85841e60075da58

Component: web-platform-tests → Layout
Product: Testing → Core

CI Results

Ran 0 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

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/567242025875 [wpt PR 32722] - [@container] Out-of-flow replaced not containers in legacy, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/906cbfdaaf1f [wpt PR 32722] - [@container] Out-of-flow replaced not containers in legacy, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.