This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17475 - http://lists.w3.org/Archives/Public/www-style/2012Jun/0200.html
Summary: http://lists.w3.org/Archives/Public/www-style/2012Jun/0200.html
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: Flexbox (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Tab Atkins Jr.
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-12 21:56 UTC by Alex Mogilevsky
Modified: 2012-07-09 22:11 UTC (History)
3 users (show)

See Also:


Attachments

Description Alex Mogilevsky 2012-06-12 21:56:24 UTC
Hypothetical main size determination in flex layout algorithm [1] has unnecessary assymetry wrt flex items parallel vs. orthogonal to main axis. The distinction is not useful, because (1) items in parallel writing mode can have orthogonal content and (2) there are other reasons for item layout to behave similar to orthogonal writing mode, e.g. a multiline flexbox with orthogonal main axis.

What matters is dependency of content max-size an min-size on cross size of flex container.

The two bullet items on laying out items in available space should be replaced with following:

<algorithm>
Otherwise, lay out the item using available space with following dimensions: 

* On main axis: 
	- if flex-basis is auto: infinite
	- if flex-basis ‘fit-available’ or ‘fit-content’:  
	  flex-container’s main size, constrained by its 
	  min and max size.

* On cross axis:  flex container’s cross size, constrained 
  by its min and max size.

The flex base size is the item's resulting measure.
</algorithm>

[1] http://dev.w3.org/csswg/css3-flexbox/#hypothetical-main-size
Comment 1 Tab Atkins Jr. 2012-07-09 22:11:56 UTC
Fixed.