W3C home > Mailing lists > Public > www-style@w3.org > September 2011

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

From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
Date: Thu, 22 Sep 2011 19:44:45 -0700
Message-ID: <BLU165-ds16C2B2F2C86D1EFD1E451F80F0@phx.gbl>
To: "Ojan Vafai" <ojan@chromium.org>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style list" <www-style@w3.org>
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 Friday, 23 September 2011 02:45:15 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:04 UTC