Re: [csswg-drafts] [css-nav-1] Reordered sequential navigation (#3377)

> It seems like an overstatement to say that 2D has no inherent order, quite a lot of it does.

I know, and I am saying that there isn't in an intentionally provocative statement. In a document-like thing, you tend to have a pretty strong order nonetheless. In an an app-like thing, it's a lot less clear. Local areas tend to be ordered, but at the top level less so. Is the toolbar before the side panel? ¯\_(ツ)_/¯

So, while I do agree my statement is too strong, I do think that assuming "The visual order" is a thing on par with "The document order" is misleading. And since we're so used to the document order, a bit of a provocative statement seems constructive.

That said, I think you have a point saying that in many case, trouble comes from the fact that there are many cases where even though the document order exists, it isn't particularly meaningful, so authors tend to feel free to place things visually with little regards for the document order, and navigation ends up being erratic.

In general, I think things like flexbox and grid etc should continue to follow document order when dealing with sequential navigation, as there are many cases where document order is meaningful. But thinking of it, maybe there should be something in the markup to indicate "the descendants of this element are not strongly ordered semantically", in which case sequential navigation should be informed by the visual placement of things more than by document order.

If this switch should exist, I feel quite strongly that its proper place is in markup, not in css.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3377#issuecomment-443914905 using your GitHub account

Received on Monday, 3 December 2018 23:49:47 UTC