Flexbox flex-bias influenced by TextArea input does not match that of Input type='text'
Reported by
kevin.jo...@redfin.com,
Apr 26 2016
|
||||||||||||
Issue description
Chrome Version : 49.0.2623.110
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: Pass
Firefox: Pass
IE: ???
What steps will reproduce the problem?
(1) Open example fiddle https://jsfiddle.net/pjd6vm0k/3/ and run
(2) Resize results window to a small size
What is the expected result?
Space is "taken" from the left column in equal amounts from all three "fields" until taking space would introduce into the "hypothetical main size" and cause a content reflow.
What happens instead?
If the right hand column contains a TextArea element, the flexbox layout algorithm seems to take space from the left column at a more aggressive rate, and column widths become unmatched.
Please provide any additional information below. Attach a screenshot if
possible.
Screenshots: http://i.imgur.com/g51rAif.png
Fiddle: https://jsfiddle.net/pjd6vm0k/3/
Spec http://www.w3.org/TR/css-flexbox-1/#algo-main-item seems to say that space should be removed based on the "hypothetical main size" of the flexable box, which seems to allude to them all collapsing at the same rate until this main size is reached
,
Apr 26 2016
Sorry for not including platform info, I jumped to chome beta to see if it still repros there. OS: Mac OSX 10.11.4 (15E65) Chrome: 51.0.2704.22 beta (64-bit) I was attempting to describe slightly different behavior that when you took a screen cap of, I should have taken my own the first time. Attached now. It occurs when the window size is collapsing. The outer "column" div has max-width and begins to collapse, and you can see how the rows in the demo "form" collapse a bit differently.
,
Apr 26 2016
Wow, I really can't spell. I shouldn't work on bugs before I've had my morning coffee. Sorry for all the typos.
,
Apr 27 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 29 2016
Thanks for the update. Able to reproduce the issue on Mac 10.11.4 using 50.0.2661.94.This issue is a non regression issue seen from 29.0.1502.0. Note : Its working fine on Win 7 and Ubuntu 14.04 using stable 50.0.2661.94,51.0.2704.29 and canary 52.0.2719.0.
,
May 2 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2017
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by brajkumar@chromium.org
, Apr 26 2016Labels: Needs-Feedback
765 KB
765 KB Download