[wpt-sync] Sync PR 28853 - [ReplacedNG] Fix relayout boundary logic.
Categories
(Core :: SVG, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 28853 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/28853
Details from upstream follow.
b'Ian Kilpatrick <ikilpatrick@chromium.org>' wrote:
[ReplacedNG] Fix relayout boundary logic.
We had an issue when a replaced object was a relayout root.
With this change it was possible for a replaced element to clear its
layout results when being laid out as a layout root.When a RecalcLayoutOverflow was triggered, we'd try and perform the
CloneWithPostLayoutFragments however this would now fail, as the
replaced element fragment "PostLayout()" call would fail, as there was
no updated fragment.This change makes the replaced element go down the NGBlockNode::Layout
path when laying out from a relayout boundary.Bug: 1205852, 1205977, 1205971
Change-Id: I7f195817daddd17659564e56f7e0f3b46ec53991Reviewed-on: https://chromium-review.googlesource.com/2875638
WPT-Export-Revision: 7ea2f02ab3a91820421c0259fe54dee1721f3932
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 1•5 years ago
|
||
| Assignee | ||
Comment 2•5 years ago
|
||
CI Results
Ran 14 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
Comment 4•5 years ago
|
||
| bugherder | ||
Description
•