- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2017 03:31:13 +0000
- To: public-css-archive@w3.org
In this example, I would expect that setting `nav-right` to `auto` would be enough: there is nothing to the right, so the UA's heuristics should deal with that inteligently. It seems that an explicit none would be needed for a different case: there **is** something focusable to the right, but you don't want the focus to go there if the user navigates right. However, isn't that fairly use hostile? a mouse user would be able to focus/click on that element, but a keyboard user would either be unable to, or would have to discover a different path through the page. This problem isn't new, since `nav-*`can already make some elements inaccessible if the author isn't careful and create navigation paths that avoid them, but the risk of the none value seems larger than its benefit to me. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330418767 using your GitHub account
Received on Tuesday, 19 September 2017 03:31:05 UTC