-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ignore relpos offsets when balancing columns.
Calculate the block-size during layout that is to be used as input to the initial column balancing attempt. Do this before relative offsets are applied. Doing it after layout, like we used to, is tricky, since it's hard to un-apply relative offsets correctly at that point, both with regards to percentages, which would require a constraint space, and whatever special rules we have (grid layout) for relative positioning. This allows us to share code between column balancing and actual fragmentation. No longer need for BlockAxisLayoutOverflow() -- use BlockSizeForFragmentation() instead. This also fixes the unit test PaintPropertyTreeBuilderTest.ColumnSpannerUnderRelativePositioned when LayoutNGBlockFragmentation is enabled. Bug: 829028 Change-Id: I82c599fd01c1244f56a95f512fe6de33bb05e9fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3270688 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#940671}
- Loading branch information
Showing
8 changed files
with
109 additions
and
72 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
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
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