W3C home > Mailing lists > Public > www-style@w3.org > December 2010

RE: [css3-flexbox] Flex-align possibilities

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Tue, 21 Dec 2010 08:15:57 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928411DA7250@TK5EX14MBXC212.redmond.corp.microsoft.com>
It's been a while so I may need a reminder for what we agreed on last time. Whatever it was I remember I liked it then...

Looking at this table, I do like the Align+Margin column.

- using auto margins to align left/right/center is already well understood, so extending that to vertical alignment in horizontal flexbox looks intuitive and will immediately make sense to people.
- it may be a slight stretch that "flex-align:baseline; margin:auto 0;" may not actually center vertically, but it still makes sence.
- I certainly have bias of two properties over a combined property that is not a shorthand... IMO combined properties create complicated OM, and they are harder to use too, especially if same word can be used in more than one position.

Of 2,3 and 7 "align+margin" can do 2 and 7 -- seems good too.

Do you have any new concerns that make other options attractive? Keeping the old draft is less work for me of course, but you managed to convince me earlier that separate control of align and baseline is important...

Alex

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Tab Atkins Jr.
Sent: Monday, December 20, 2010 4:30 PM
To: www-style list
Subject: [css3-flexbox] Flex-align possibilities

I'm merging the changes that Alex and I agreed on into the Flexbox spec right now, and I'm still not quite sure what I want to do about flex-align.  I've got a couple of choices, which I've illustrated
here: <http://www.xanthir.com/diagrams/flex-align-diagrams.html>.
(Use Firefox - Webkit has a bug regarding box-sizing and percentage heights on elements in table-cells that screws up the 'stretch'
diagrams, and I dunno about other browser's box-sizing support because I don't have them on my current box.)

As you can see by the diagram, there a bunch of possibilities.  At minimum, we should support 1, 6, 13, 14-17, and either 2, 3, or 7.
The other cases may or may not be useful; align+switch cuts out all the other ones.

So, bikeshed time.  What seems best?  They're all roughly equal from a spec-writing perspective.

~TJ

Received on Tuesday, 21 December 2010 08:16:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:35 GMT