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

[css-flexbox]the 'auto' value should be add to 'flex-basis' ? #329

Closed
p2227 opened this issue Jul 19, 2016 · 3 comments
Closed

[css-flexbox]the 'auto' value should be add to 'flex-basis' ? #329

p2227 opened this issue Jul 19, 2016 · 3 comments
Labels
Closed Rejected as Invalid Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-flexbox-1 Current Work Tracked in DoC

Comments

@p2227
Copy link

p2227 commented Jul 19, 2016

https://www.w3.org/TR/css-flexbox-1/#flex-basis-property

should

Value:  content | <‘width’>

be

Value: auto | content | <‘width’>

??

@frivoal
Copy link
Collaborator

frivoal commented Jul 19, 2016

auto is part of <'width'> already.

@frivoal frivoal added the css-flexbox-1 Current Work label Jul 19, 2016
@p2227 p2227 closed this as completed Jul 20, 2016
@fantasai fantasai added the Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. label Mar 15, 2017
@chharvey
Copy link

This is confusing because the auto value for flex-basis behaves differently than the auto value for width (or height). And what's worse, if you want the width (or height) to be 'automatically sized', you must use flex-basis: content.

Because the auto keyword, even though already part of the <'width'> syntax, behaves differently, I completely understand @p2227's mistake in missing it. What a pedagogical nightmare!

May I suggest setting auto to trigger the 'automatic sizing' behavior, as it is for <'width'>, and introduce a new keyword defer, which would mean "look at my width or height property"?

@frivoal
Copy link
Collaborator

frivoal commented May 1, 2017

I'm afraid this suggestion comes a few years too late. Implementations have shipped, and web content depends on it. In addition to making the point that this would be a good idea, if you want this to happen, I think you need to present evidence that making this change would not result in many web-sites breaking, which I doubt is possible.

@fantasai fantasai added this to the Published css-flexbox-1 2017-10-19 milestone Mar 29, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed Rejected as Invalid Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-flexbox-1 Current Work Tracked in DoC
Projects
None yet
Development

No branches or pull requests

4 participants