Closed
Bug 1486688
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 12714 - [LayoutNG] Fix legacy initiated abspos invalidation
Categories
(Core :: CSS Parsing and Computation, enhancement, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 12714 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12714 Details from upstream follow. Aleks Totic <atotic@chromium.org> wrote: > [LayoutNG] Fix legacy initiated abspos invalidation > > Bug: > > LayoutBlock::LayoutPositionedObject had a static position check whether > child reflow was necessary: > if (.... || > (!IsLayoutNGBlockFlow() && > NeedsLayoutDueToStaticPosition(positioned_object)))) > layout_scope.SetChildNeedsLayout(positioned_object); > This check would skip reflow for all NGBlockFlow children. > This is incorrect. If child abspos layout was initiated by Legacy, > we should check static position. > > Fix: > There was no way to tell in current code whether child abspos layout > was initiated by legacy. > Added a flag is_legacy_initiated_out_of_flow_layout_. > Flag was added to LayoutBlock per ikilpatrick recommendation. > Flag is set to true in LayoutNGBlockFlow::UpdateOutOfFlowBlockLayout > Flag is set to false in NGOutOfFlowLayout. > > With this fix, checkboxes on code review page are correct. > > Bug: 863865 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng > Change-Id: Ifc55ac03b76dd1aa2113181681bca1b5a2832fb2 > Reviewed-on: https://chromium-review.googlesource.com/1190723 > WPT-Export-Revision: ba6551676ab7b95020dd5551c121a56c03bf6467
Assignee | ||
Updated•6 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 1•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=a8504ff06031ac2e88794672bdbac36bcc7923f8
Assignee | ||
Comment 2•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=0907284556416ca6fe633666266b7aa4f5a75439
Assignee | ||
Comment 3•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=181bfd33f7a0993557a50c37182e78fe9aa8a30f
Assignee | ||
Comment 4•6 years ago
|
||
Ran 1 tests PASS : 1
Assignee | ||
Comment 5•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=6d8d2020e67090d87ef8ddda30d181ea0e3d9098
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/cd2b67d1e1e5 [wpt PR 12714] - [LayoutNG] Fix legacy initiated abspos invalidation, a=testonly
Comment 7•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cd2b67d1e1e5
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•