- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Aug 2017 12:00:24 +0000
- To: public-css-archive@w3.org
Regarding absolutely positioned elements, the order still depends on their actual visual position within the document. So, regarding your example, in an LTR context the order would be `#b2`, `#b1`, `#b3`. But note, the `nav-order` is **expected to be set on the container**, not the items. For fixed positioned or sticky elements I can imagine different options: 1. Visual order 2. Structural order 3. First in order 4. Last in order As a user I'd probably still expect to access them in visual order. To be clear, I define the visual order as the initial placement of the elements within the document before scrolling. So, e.g. having a fixed header with a search field and login fields and scrolling down the page would focus those fields before other elements further down the document. I'm not sure whether there's a need for allowing to change the navigation direction via the Flexbox keywords, because the elements may not be aligned in rows or columns, as your example shows. Especially `row-reverse` and `column-reverse` don't make sense in this context, in my opinion. But I may just miss the use case here. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1764#issuecomment-326274118 using your GitHub account
Received on Thursday, 31 August 2017 12:00:21 UTC