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

[FlexNG] Detect when a descendant's scrollbars change. #25901

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

We currently have relayout logic to detect when a flex-items scrollbars
change (to relayout) as this typically changes the min/max sizes.

However this didn't account for an arbitrary descendant changing
scrollbar state. This resulting in inconsistent sizes between a flexbox
and a flex-item.

Bug: 1127415
Change-Id: Ib2427f655437b1aa82dda2e0340fe950b079667f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424899
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812389}

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.

We currently have relayout logic to detect when a flex-items scrollbars
change (to relayout) as this typically changes the min/max sizes.

However this didn't account for an arbitrary descendant changing
scrollbar state. This resulting in inconsistent sizes between a flexbox
and a flex-item.

Bug: 1127415
Change-Id: Ib2427f655437b1aa82dda2e0340fe950b079667f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424899
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812389}
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