Closed Bug 1745956 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 32017 - [LayoutNG] Don't allow first tier OOF cache when fragmenting

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
97 Branch
Tracking Status
firefox97 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Alison Maher <almaher@microsoft.com> wrote:

[LayoutNG] Don't allow first tier OOF cache when fragmenting

Caching generally doesn't work well when fragmenting, so make sure
|allow_first_tier_oof_cache_| is false when inside a fragmentation
context.

This caused an issue when setting up the OOF node to layout. We would
fail to populate |node_to_layout.offset_info.block_estimate| when the
cache was allowed, which caused a crash when trying to use the block
estimate during layout.

Bug: 1278627, 1278879
Change-Id: I69e29646c1b4d4031dd338fce4dd898dc3804a38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3331522
Reviewed-by: Ian Kilpatrick \<ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne \<mstensho@chromium.org>
Commit-Queue: Alison Maher \<almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#951235}

Component: web-platform-tests → Layout
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/223bdf0216cc
[wpt PR 32017] - [LayoutNG] Don't allow first tier OOF cache when fragmenting, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
You need to log in before you can comment on or make changes to this bug.