Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fragments may become monolithic even if the node isn't.
So ask the fragment instead of the LayoutBox. This is an old problem, and it prevented pre-paint from understanding that a monolithic fragment would be the containing block for OOF descendants (normally in block fragmentation, OOFs are direct children of a fragmentainer, but not if they are contained by a monolithic fragment, like in this case). However, with CL:4110949 the problem became more severe, since we may now force off fragmentation at the last OOF fragment (if it's inside a clipped container), making it monolithic. out-of-flow-in-multicolumn-112.html is a test for the regression, while out-of-flow-in-multicolumn-113.html is a test that would fail even without the aforementioned CL. (cherry picked from commit 7073850) Bug: 1404718 Change-Id: I68ebd5218c2bd0e3e895eaf757a90cbc8594a028 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4131528 Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1088506} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4136433 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/branch-heads/5481@{#141} Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
- Loading branch information