W3C home > Mailing lists > Public > www-style@w3.org > January 2016

Re: [css-flexbox]

From: Bruno Racineux <bruno@hexanet.net>
Date: Thu, 14 Jan 2016 22:20:35 -0800
To: Florian Rivoal <florian@rivoal.net>
CC: François REMY <francois.remy.dev@outlook.com>, Chris Lilley <chris@w3.org>, <bcampbell@us.ibm.com>, CSS public list <www-style@w3.org>
Message-ID: <D2BDCF87.A2DB6%bruno@hexanet.net>

On 1/14/16 2:05 AM, "Florian Rivoal" <florian@rivoal.net> wrote:
>>That's precisely what I am using it for in RWD 'orientationChange'
>>context.
>
>So the markup should match the mobile ordering, since that's the intended
>linear
>reading order, and the desktop styling should use order to put the main
>content
>(which is first in the DOM) in the middle (which is first in perception),
>and move the navigation to its left, where it draws less attention and is
>seen last.

Sure, but it's a bit too simplistic an example to reflect many possible
cases. And I am not suggesting involving the primary landmark elements in
the reordering. (I would not use or recommend flexbox at the body level
like that anyway, due to unnecessary reflows or other possible problems)

The use of flexbox re-ordering is primarily targeted at the content within
those landmarks, or the landmark itself being the flex wrapper. Main
navigation isn't likely to be an issue, as it often turns into a popup
menu, with often a fixed nav position (and where its original desktop
position may not matter that much). Submenus/subnavs within the main
content may however be involved in reordering. For me, the necessity so
far, is a visual reorganization of smaller items, mainly from the main
<header> or in the breadcrumb surrounding area, to keep as much as
possible as the screen shrinks. Which can also involve a few
position:absolute(s) combined with flexbox.
Received on Friday, 15 January 2016 06:21:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:33 UTC