RE: [css3-flexbox] Too many flex-flow values?

Hi Andrew,

These are great scenarios, but I don’t think they necessitate a separate physical coordinate system.  The author is in control of the direction for any given element.  If they want the first column grid line always on the left, then they can ensure the direction assigned to the grid element is left to right.  They can do that even if they’ve established an rtl direction for the rest of the document.

In my experience, most scenarios benefit from having an element’s layout adapt to direction.  It seems reasonable to me to have authors set an additional attribute or define an additional CSS rule for an element to handle the less common scenarios.


From: [] On Behalf Of Andrew Fedoniouk
Sent: Thursday, September 22, 2011 7:45 PM
To: Ojan Vafai
Cc: Tab Atkins Jr.; www-style list
Subject: Re: [css3-flexbox] Too many flex-flow values?

Consider something close to tiled map implementation where element-tiles
shall go in strictly physical order no matter of base UI directionality.
That is one of practical situations we’ve bumped into with our flex/flow
implementation that used only logic directions initially.

Another case is when content contains explicit mentioning of
the direction, like: “Result of formula (on the left) is presented in
the table on the right”. It is better to use physical directions here
for many reasons including potential misinterpretation of information
when blind translations are used.

Obviously this applies to flexbox and grid use cases.

Andrew Fedoniouk

From: Ojan Vafai<>
Sent: Thursday, September 22, 2011 5:08 PM
To: Andrew Fedoniouk<>
Cc: Tab Atkins Jr.<> ; www-style list<>
Subject: Re: [css3-flexbox] Too many flex-flow values?

Can you give use-cases where logical directions are insufficient. It's hard to argue against "for ttb systems use of only logical directions in Grid is plainly wrong" because it doesn't actually say what's wrong or what use-cases don't work.

Received on Sunday, 25 September 2011 09:00:58 UTC