[LayoutNG] Initial support for column-span:all.
This adds support for the fundamentals required by column-span:all. We still don't attempt to position the spanners correctly. We need to margin-collapse between spanners and calculate the inline position first. We also still don't support breaking between spanners, or between column rows and spanners. This may be necessary if we're nested inside another fragmentation context. Spanners are detected during regular column layout, and will bubble up to the column layout algorithm, where they will be laid out as children, before regular column content resumes. The column content will see the spanner as a forced column break. Some tests now start to fail. Two dynamic tests fail because NGPaintFragment doesn't really understand block fragmentation. One starts to crash, because a spanner causes a break inside the containing block of an out-of-flow positioned descendant, which we have never supported anyway. See crbug.com/996655 Bug: 829028 Change-Id: I60229da59f745dd469bbf104f6f46e5f93e1a1de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771909 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#691548}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment