"contain: content" after "display: initial" makes block element disobey size properties
Reported by
joonas.m...@smartly.io,
Aug 13
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. Give a block element this style: `display: initial; height: 100px; width: 100px; contain: content` What is the expected behavior? The `display` property of the element should be `block` (from initial) and thus it should be sized to 100x100 properly. Instead, the size of the element equals content size. What went wrong? The element is not sized in the Chrome beta release, but is sized in stable. See screenshot (left is stable, right is beta) Did this work before? Yes 68.0.3440.106 (Official Build) (64-bit) Does this work in other browsers? Yes Chrome version: 69.0.3497.32 (Official Build) beta (64-bit) Channel: beta OS Version: OS X 10.13 Flash Version:
,
Aug 14
Able to reproduce issue on reported chrome version 69.0.3497.32 & on latest chrome 70.0.3521.0 using Windows 10,Ubuntu 17.10 and Mac 10.13.3. Hence providing bisect information below. Bisect Info: ================ Good build: 68.0.3440.106 Bad build: 69.0.3441.0 CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/598bfbd8dad098680e084b02b07cf8efe0ababb7..c42d28a2c412eebb39c96e81d1a08191be7cb404 suspect: https://chromium.googlesource.com/chromium/src/+/c42d28a2c412eebb39c96e81d1a08191be7cb404 Reviewed-on: https://chromium-review.googlesource.com/1071794 rego@: Please confirm the issue and help in re-assigning if it is not related to your change. Adding 'ReleaseBlock-Stable' label for M-69 as this is a recent regression. Please feel free to remove if this is not applicable. Thanks!
,
Aug 14
Since rego@ is OOO cc'ing CL reviewers.
,
Aug 14
display: initial is display: inline, so I think this is very much intended given that changeset.
,
Aug 14
initial is indeed inline, closing as per comment 4. |
||||
►
Sign in to add a comment |
||||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 13