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

Re: [css3-flexbox] flexbox algorithm and writing modes

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 25 Apr 2012 09:01:49 -0700
Message-ID: <CAAWBYDCbRMyd7WvG0TK68Ht+UZQJ_xDPGGP5C7n0t7Km33eBDg@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On Wed, Apr 25, 2012 at 8:29 AM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
> ± From: fantasai [mailto:fantasai.lists@inkedblade.net]
> ± Sent: Friday, April 20, 2012 4:03 PM
> ±
> ± There are several places in the Flexbox algorithm where it seems assumed that
> ± the writing mode of the flexbox item is the same as that of the flexbox. This
> ± isn't a true assumption, so the algorithm needs to be fixed to define these
> ± cases.
>
> Can you point at such places? Flexbox is generally agnostic to what happens inside the items, including their inner layout type and most certainly writing mode. Issues of mixed writing modes have to be addressed in writing-modes spec or in specs for individual layout types (for issues of being inside a parent with a different writing mode)...
>
> If there are still places where flexbox spec says something that implies same writing mode in a child, it must be corrected.
>
> Perhaps you refer to baselines? Column-direction flexbox always treats 'baseline' alignment as 'center', while its children can have baselines in block direction. We should fix that.
>
> What else?

I believe fantasai and I have fixed all of the places where this
occurred.  It was mostly just in the "hypothetical main size of items"
step, because that ends up invoking some subtle behavior with a lot of
possible combinations.

~TJ
Received on Wednesday, 25 April 2012 16:02:44 GMT

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