- From: Jihye Hong via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2017 00:47:53 +0000
- To: public-css-archive@w3.org
> 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. Yes, you're right. `none` value causes some unreachable problems for the navigation. As you said, the example above can be solved another way. : ) -- GitHub Notification of comment by jihyerish Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1822#issuecomment-330713355 using your GitHub account
Received on Wednesday, 20 September 2017 00:48:15 UTC