-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prevent OOFs in clipped containers from adding more fragmentainers.
If the containing block of an out-of-flow positioned box is inside a overflow-clipped container inside a fragmentation context, prevent the out-of-flow positioned box from generating additional fragmentainers. An OOF will have its fragments placed as direct children of fragmentainers, so any clipping caused by actual ancestor in the real containing block chain will not be detected during layout. Therefore, when reaching the last fragmentainer seen (so far), force the OOF node to finish there, placing all its remaining content in the last fragmentainer. Anything overflowing the clipped container will be clipped during paint / pre-paint - normally. This isn't a perfect solution, since the clipped container doesn't necessarily end in the last fragmentainer created so far. It may end earlier. This is to say that this fix doesn't catch every problem in this area. But hopefully good enough for now. (cherry picked from commit 1f5612e) Bug: 1399313 Change-Id: I27be47bd09d7212abd6aea0715e1cc8fe0b3440d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4110949 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1086314} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4131396 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Morten Stenshorne <mstensho@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5481@{#98} Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
- Loading branch information
Showing
16 changed files
with
231 additions
and
39 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
Oops, something went wrong.