- From: Christian Biesinger <cbiesinger@chromium.org>
- Date: Fri, 22 Mar 2013 16:15:33 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>, Ojan Vafai <ojan@chromium.org>
[resending slightly modified from the right address] On Fri, Mar 22, 2013 at 4:05 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Fri, Mar 22, 2013 at 2:33 PM, Christian Biesinger > <cbiesinger@chromium.org> wrote: >> On Wed, Mar 20, 2013 at 4:24 PM, Christian Biesinger >> <cbiesinger@chromium.org> wrote: >>> On Wed, Mar 20, 2013 at 4:03 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >>>> For guidance, check out the Flexbox Baselines section >>>> <http://dev.w3.org/csswg/css3-flexbox/#flex-baselines>, which is very >>>> precise and explains how to handle cases when there's no appropriate >>>> baseline in a particular direction. >> >> Upon re-reading the baseline paragraph, I noticed that it only applies >> to table cells (and grid and flex). > > I think you're misreading, or reading too much into it. > > The paragraph about table-cells is because, when doing baseline > alignment for table cells, it's specified that only a specific subset > of children are looked at to find the baseline of the cell. In > particular, blocks are ignored, so that it can find some text instead. > That paragraph makes sure that it looks at flexboxes as well. > > No other layout modes skip over children like that, so nothing needed > to be said about them. Ah. I wonder if the text can be clarified. Maybe something like "Applies to block containers, flex items and grid items. For the last three, aligns ...". There's other paragraphs in the spec that start with "For (this thing)" and end with "Otherwise, treat as (a different value)" so I was assuming this was the case here too. -christian
Received on Friday, 22 March 2013 23:16:01 UTC