- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 21 Mar 2014 17:44:31 -0700
- To: Daniel Holbert <dholbert@mozilla.com>
- Cc: Peter Salas <psalas@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Feb 13, 2014 at 2:33 PM, Daniel Holbert <dholbert@mozilla.com> wrote: > On 02/13/2014 01:10 PM, Peter Salas wrote: >> The relevant part of the editor's draft seems to be section 9.8: >> >> "The main-size min-content/max-size contribution of a flex item is its outer hypothetical main size when sized under a min-content/max-size constraint (respectively)." >> >> The first rule for calculating the hypothetical main size is to use the flex basis, but is 9.8 saying that the flex basis should be ignored for calculating the min-content/max-size contributions? > > This looks to me like just an oversight/bug in Chrome & Firefox. > > I think it makes more sense to use the (flex-basis-based) hypothetical > main size, as you suggest & as the spec seems to require. That way, we > won't end up with weird cases where an auto-sized flex container has way > too much (or too little) space. > > (I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=972595 to fix > this in Gecko, as long as there's agreement here on what the correct > behavior should be.) As far as I can tell, the spec already says this. 9.8 says to use the hypothetical main size, when sized under a min/max constraint. Following that link, the hypothetical main size calculation uses the flex-basis to figure things out. Am I missing something, or is this already taken care of? ~TJ
Received on Saturday, 22 March 2014 00:45:20 UTC