Closed
Bug 1840751
Opened 2 years ago
Closed 2 years ago
[wpt-sync] Sync PR 40780 - Ensure OOF fields on LayoutResult after subtree layout
Categories
(Core :: DOM: CSS Object Model, task, P4)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
FIXED
117 Branch
Tracking | Status | |
---|---|---|
firefox117 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 40780 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/40780
Details from upstream follow.
Xiaocheng Hu <xiaochengh@chromium.org> wrote:
Ensure OOF fields on LayoutResult after subtree layout
This prevents a crash introduced by crrev.com/c/4583533, which assumes
that oof fields are set on NGLayoutResult on every OOF node, which is
tree after full layout but not subtree layout. This patch ensures it for
the latter case.Bug: 1458561
Change-Id: If4d3bddf4c21caffb05d3a027471782780c7dc0a
Reviewed-on: https://chromium-review.googlesource.com/4651940
WPT-Export-Revision: 8b97a12899dc12affd9d1b2668d9e84291cc75dd
Assignee | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•2 years ago
|
Component: web-platform-tests → DOM: CSS Object Model
Product: Testing → Core
Assignee | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 1•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=ad97e1f14dad11eaa9720189ed71d63fd4dda30b
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c6156ffde3d6
[wpt PR 40780] - Ensure OOF fields on LayoutResult after subtree layout, a=testonly
Assignee | ||
Comment 3•2 years ago
|
||
Test result changes from PR not available.
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox117:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•