Closed Bug 1753965 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 32721 - [@container] Resume skipped style recalc for dropped LayoutObjects

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

[@container] Resume skipped style recalc for dropped LayoutObjects

LayoutObject::IsChildAllowed() may disallow child LayoutObjects of
certain types. We are typically not able to detect this at style recalc
time, which means we may skip style recalc for size query containers
which will not be able to resume recalc in NGBlockNode. Detect this at
AttachLayoutTree time and force-resume the style recalc like we do for
legacy layout.

Bug: 1294268
Change-Id: I0a1a3d4437d84d913c3a75b056ae993601a5fb51
Reviewed-on: https://chromium-review.googlesource.com/3440249
WPT-Export-Revision: b67757bf264a0c5663c5115f00196257b513ce79

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/4262b959ee05 [wpt PR 32721] - [@container] Resume skipped style recalc for dropped LayoutObjects, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/57673d6c0d3f [wpt PR 32721] - [@container] Resume skipped style recalc for dropped LayoutObjects, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.