New issue
Advanced search Search tips

Issue 816477 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Table within vertical flexbox expands horizontally

Project Member Reported by larsrc@google.com, Feb 26 2018

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Put a table inside a vertical flexbox, where the flexbox is wider than the table contents.

JSFiddle: https://jsfiddle.net/Lboqj6jv/2/

What is the expected result?

The table uses only the width it needs (Chrome 64 behaviour)

What happens instead?

The table widens to fill horizontally (Chrome 65 behaviour)

Please use labels and text to provide additional information.

Not sure if this is an intended change or a regression. I don't see any related issues slated for M65.

See also live example in the cross-references panel at e.g. https://cs.chromium.org/chromium/src/v8/src/string-stream.h?type=cs&q=string&sq=package:chromium&l=32

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by tkent@chromium.org, Mar 8 2018

Components: Blink>Layout

Comment 2 by e...@chromium.org, Mar 16 2018

Cc: dgro...@chromium.org
Owner: mstensho@chromium.org
Status: Assigned (was: Untriaged)
Is this a dup of the other table percentage issue?
But there's no flexbox in the test! I guess that's a mistake (since the description mentions flexbox), and that this is about  bug 821832 , but it would nice if larsrc could provide a testcase that clearly demonstrates the problem.

Comment 4 by larsrc@google.com, Mar 16 2018

Sorry, the flexbox part fell out trying variations. Added it back, together with a flex-less version that behaves differently.

Reading more closely, I think this is actually an anti-regression: You're now complying with the the default "stretch" flexbox. This is just going to cause some... differences.

Feel free to close this (I don't seem to be able to).
Is the correct test URL https://jsfiddle.net/Lboqj6jv/16/ ? That was the highest revision I could find.

Comment 6 by larsrc@google.com, Mar 16 2018

v/16 is correct (modulo some stray </div>s that didn't affect the result)
Status: WontFix (was: Assigned)
Thanks. Yes, then this is actually an improvement, not a regression. But it was introduced by the same CL that caused  bug 821832 . :)

Sign in to add a comment