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] Add percentage_resolution_block_size into the min/max pass. #15322

Merged
merged 1 commit into from Feb 12, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

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

This was surprising to me! But the min/max sizes depend on the
percentage resolution block-size, as replaced elements reflect this
size into their width.

This was working previously as the replaced element was manually
computing the heights, but this adds it into the pass explicitly.

This fixes it for absolute positioned objects which use the current
final height as the input to this function.

Eventually we'll want to cache based off this, and record if there is
a replaced element with percentage block-size in the calculation chain.

Bug: 635619
Change-Id: I6db9a90007b6c7d70f51d5ae1209ffba8a629e03
Reviewed-on: https://chromium-review.googlesource.com/c/1456203
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631236}

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.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1456203 branch 2 times, most recently from 320a0dd to 35ef98b Compare February 12, 2019 05:03
This was surprising to me! But the min/max sizes depend on the
percentage resolution block-size, as replaced elements reflect this
size into their width.

This was working previously as the replaced element was manually
computing the heights, but this adds it into the pass explicitly.

This fixes it for absolute positioned objects which use the current
final height as the input to this function.

Eventually we'll want to cache based off this, and record if there is
a replaced element with percentage block-size in the calculation chain.

Bug: 635619
Change-Id: I6db9a90007b6c7d70f51d5ae1209ffba8a629e03
Reviewed-on: https://chromium-review.googlesource.com/c/1456203
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631236}
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