tree f1a78b51b972d064ac5b52b3359b87625e56b1b8
parent add24188a1226f3598ad6b455e71641c9ac6a5fd
author Aleks Totic <atotic@chromium.org> 1553921607 -0700
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> 1553922190 -0400

[LayoutNG] Fix nested legacy oof descendants

Another fix for "Legacy OOF descendant did not get laid out"

The cause here was:
- if #container had a legacy descendant, and
- legacy descendant had an oof descendant whose containing block was
#container, that oof descendant would get added to #container's list
of legacy oof, but would never get laid out.

This bug was hidden, because it would not happen if layout happened
twice, which we often do.

Seen in the wild at https://www.humblebundle.com/ when scrolling down.

Bug: 946986
Change-Id: I183f3d5dfe79b49c5c6aadad0ee2cfcb8bb6849f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546713
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#646077}