Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Column spanner margins may collapse through OOF siblings.
If there's column spanner A, then some out-of-flow content not part of the fragmentation context, then another spanner B, the block-end margin of spanner A should collapse with the block-start margin of spanner B, as no columns should be created for the out-of-flow content (as far as the spec is concerned). See w3c/csswg-drafts#6265 In our implementation we DO create column fragments for such out-of-flow content, though, as we need this to let the OOFs bubble all the way up to their containing block. Therefore, let spanner margins collapse through such "empty" column rows. We'll now update the intrinsic block-size of the multicol and reset the margin strut only of the column row is considered to be non-empty. As a consequence of this, we need to avoid using intrinsic_block_size_ in some cases, but rather require that a row offset be supplied (it's actually quite tempting to just remove intrinsic_block_size_ completely as a member, since it's hard to determine when it's safe to use and not). This fixes two failing tests. Note that there's still one test failing (fast/multicol/relpos-becomes-static-has-abspos.html) because of this problem. Note that there was actually remnants of code that attempted to deal with this, but it got messed up by CL:2410242. Bug: 1151880 Change-Id: I990d42f7b4661bac50ad52f65d40d902cb79249e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2998709 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#897948} NOKEYCHECK=True GitOrigin-RevId: 48f75c5d7e2142b979f48f0498df0b5849b87d97
- Loading branch information
Showing
3 changed files
with
53 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters