[LayoutNG] Detect breaks that occur at the exact start of blocks.
Such breaks used to go unnoticed and cause misery and assorted unpleasantries. Upgraded test expectations. Added a unit test. As long as we haven't both got an in-flow child that broke AND exceeded available fragmentainer space, we need to continue and lay out its siblings. A block of zero height at a fragmentainer boundary actually belongs in the former fragmentainer, not the latter. A consequence of this change is that even non-zero height blocks that start at a fragmentainer boundary gets a zero-height fragment in the former fragmentainer, before it continues in the next fragmentainer. We may want to avoid this, but I'm not sure what's more correct yet (or if it matters at all). Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I50e862d8c0dc787a47b799e2e639e5ca7ba57158 Reviewed-on: https://chromium-review.googlesource.com/663141 Commit-Queue: Morten Stenshorne <mstensho@opera.com> Reviewed-by:Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#501588}
Showing
Please register or sign in to comment