Oh wait, it looks like you're talking about the old flexbox spec. Disregard my email. On Fri, Dec 2, 2011 at 3:00 PM, Tony Chang <tony@chromium.org> wrote: > The current version of the spec doesn't say what to do with margin: auto, > although previous versions said to treat it as flex(1). We have been > treating margin: auto as margin: 0. > > I think the reason Tab gave for removing the margin:auto behavior was that > it was redundant with what flex-align already provides. > > > On Fri, Dec 2, 2011 at 2:31 PM, Alex Mogilevsky <alexmog@microsoft.com>wrote: > >> Trying to understand what exactly is expected from flexbox alignment, I >> came up with a test that is exercising all alignment/size/margin >> combination I could think of. The new spec ( >> http://www.w3.org/TR/css3-flexbox/#flex-align) is not yet specific >> enough, but I am pretty sure we have agreed that we will want same behavior >> as specified in 2009 spec ( >> http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/#alignment), at least >> I am not aware of any stated differences.**** >> >> ** ** >> >> Attached is the test, including prefixed syntax for implementations I >> know about >> (-ms-box-, -moz-box- and -webkit-box-) and a screenshot of what I expect >> to see. ** ** >> >> ** ** >> >> Is my understanding correct?**** >> >> ** ** >> >> Note that as far as I can read the 2009 spec, it does “true center” both >> when aligned with margins and when aligned with “box-align:center”. Not >> sure if it was intentional but it is what it defines, doesn’t it?**** >> >> ** ** >> >> Also note that the test includes all cases in horizontal and in vertical >> writing modes. I only included a screen shot for horizontal, writing mode >> is there for completeness but it doesn’t make any difference for flexbox >> algorithms.**** >> >> ** ** >> >> Thanks**** >> >> Alex**** >> >> ** ** >> > >
Received on Friday, 2 December 2011 23:04:29 UTC