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

[layout] Track inflow-bounds within box fragment builder. #25892

Merged
merged 1 commit into from Oct 1, 2020

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Sep 30, 2020

This patch tracks the bounds of any inflow children (no floats, or
out-of-flow positioned objects).

This is only done for scrollable containers.
This is used to correctly determine the layout-overflow of a fragment.

Bug: 1066616
Change-Id: I334176cdf61f6eda92573e169719dbf7a2f62995
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432225
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812667}

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.

This patch tracks the bounds of any inflow children (no floats, or
out-of-flow positioned objects).

This is only done for scrollable containers.
This is used to correctly determine the layout-overflow of a fragment.

Bug: 1066616
Change-Id: I334176cdf61f6eda92573e169719dbf7a2f62995
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432225
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812667}
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