Navigation Menu

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] Auto block-size shouldn't prevent child margin propagation. #18993

Merged
merged 1 commit into from Sep 13, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Sep 11, 2019

The block-end margin strut of a child can collapse with the block-end
margin strut of the parent if the computed block-size of the child is
auto. This includes unresolvable percentages (e.g. if the child has a
percentage block-size, but its containing block has auto block-size).

Update BlockLengthUnresolvable() to consider 'auto' as unresolvable.
Also include 'min-content', 'max-content', 'fit-content' and 'none'
(for max-block-size), since that seems correct, and also allows for
simplifying code at call-sites.

Bug: 1001663
Change-Id: I28decd41ca8f8340581fc68e0a4fe709d7389af8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796372
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#696253}

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.

Already reviewed downstream.

The block-end margin strut of a child can collapse with the block-end
margin strut of the parent if the computed block-size of the child is
auto. This includes unresolvable percentages (e.g. if the child has a
percentage block-size, but its containing block has auto block-size).

Update BlockLengthUnresolvable() to consider 'auto' as unresolvable.
Also include 'min-content', 'max-content', 'fit-content' and 'none'
(for max-block-size), since that seems correct, and also allows for
simplifying code at call-sites.

Bug: 1001663
Change-Id: I28decd41ca8f8340581fc68e0a4fe709d7389af8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796372
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#696253}
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