Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LayoutNG] Handle kOutOfFragmentainerSpace result types for OOFs #31975

Merged
merged 1 commit into from Dec 9, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Dec 9, 2021

If we hit kOutOfFragmentainerSpace when laying out an OOF, add
it to the list of elements to continue in the next fragmentainer,
as if it had a break before.

Crash test added.

Bug: 1278350
Change-Id: Iddd9b97ef54e78e7605250da55a6dde687d5bd9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328442
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#950334}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

If we hit kOutOfFragmentainerSpace when laying out an OOF, add
it to the list of elements to continue in the next fragmentainer,
as if it had a break before.

Crash test added.

Bug: 1278350
Change-Id: Iddd9b97ef54e78e7605250da55a6dde687d5bd9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328442
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#950334}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants