Closed Bug 1499529 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 13550 - [css-flexbox] Apply min-height: auto to nested flexboxes again

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla65
Tracking Flags:
Tracking Status
firefox65 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

Sync web-platform-tests PR 13550 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/13550
Details from upstream follow.

Christian Biesinger <cbiesinger@chromium.org> wrote:
>  [css-flexbox] Apply min-height: auto to nested flexboxes again
>  
>  This was made possible by crrev.com/c/1283482, which avoids the
>  performance and correctness issues this previously caused.
>  
>  This relands crrev.com/c/1246730 / crrev.com/c/1252682. The ChromeOS UI
>  breakage was fixed by crrev.com/c/1281726 and crrev.com/c/1282462
>  
>  IF THIS BREAKS ANY FURTHER CHROME UI:
>  Please don't revert this patch; instead, add min-height: 0 to any
>  inner nested flexboxes that may be affected by this patch. This is
>  an important change for web interop with the other browsers.
>  
>  Bug: 596743
>  Change-Id: I9afe54dce82d41da452d1fdca8150ca22ebb6f9c
>  Reviewed-on: https://chromium-review.googlesource.com/1269235
>  WPT-Export-Revision: 751f0a6d5ba28f9d4e0545ba3fef3eba47be7464
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 1 tests
PASS   : 1
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/06aeec485368
[wpt PR 13550] - [css-flexbox] Apply min-height: auto to nested flexboxes again, a=testonly
https://hg.mozilla.org/mozilla-central/rev/06aeec485368
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.