W3C home > Mailing lists > Public > www-style@w3.org > May 2012

RE: [css3-flexbox] List of Issues

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Wed, 9 May 2012 23:53:52 +0000
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <2C86A15F63CD734EB1D846A0BA4E0FC81A3F2BE6@CH1PRD0310MB381.namprd03.prod.outlook.com>
 From: fantasai [mailto:fantasai.lists@inkedblade.net] 
 Sent: Tuesday, May 08, 2012 1:27 PM
 List of issues that need WG resolution, Take I.
    4. Applicability of flex-basis: is it used or ignored for flex == 0?
       Alex suggests it is ignored:
       This would make main sizing source property different iff
       flex-grow == flex-shrink == 0.

Have I actually proposed that flex-basis is ignored when there is no flexibility? That thread was complicated...

Is the question here what does this mean, right?

	"flex:0 0 0px; width:100px"

Will the item be 0px or 100px?

I am not sure what's better. Probably 0px will be more consistent and at the moment I can't think of a strong use cases for the opposite.

    2. Stretch doesn't allow shrinkage, is that what's wanted?
   3. Get WG approval of 'auto' margin behavior (which is designed to match Grid atm)
      Also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16755

   4. How do auto margins affect an element's participation in baseline alignment?

   5. 'distribute' behavior doesn't match use case that prompted it

    6. Define/resolve on alignment fallbacks for baseline, stretch, distribute, 

[am] not sure what this one is about... if it is more about baseline, there was an email thread where Tab disagreed with my statement that baseline should always work and doesn't need a fallback (http://lists.w3.org/Archives/Public/www-style/2012Apr/0746.html). We discussed it later and you seemed to agree with me.

    3. Rename 'flex-order' to 'box-order', since it doesn't affect order of
       flexing, but order of boxes.
       Note: this also allows re-use of the property in e.g. grid auto-placement.

My concern with this (and any other renames that would drop "flex-" prefix) is that if the property has effect outside flexbox, can it be implemented without a vendor prefix while it only works in flexbox? 

Received on Wednesday, 9 May 2012 23:54:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:16 UTC