- From: Hugo via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 May 2019 12:37:32 +0000
- To: public-css-archive@w3.org
> For example, the element specified with "visibility: hidden", is it a focusable or not? IMO, [things users can't see](https://chromium-review.googlesource.com/c/chromium/src/+/1628612) should _not_ be navigable. Nodes with a key- or click handler most likely [_needs_ to be navigable](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/dom/element.cc?type=cs&q=SupportsSpatialNavigationFocus&sq=package:chromium). Some web apps use one "catch all"-click handler, often put on `body` or a container `div`, to react on clicks within certain sub areas of the page. These web apps often lack tab indices. Instead, clickable/focusable elements, for example `div`s that look like buttons, are styled with `cursor: |pointer|`. To enable SpatNav on these web apps, let's add `cursor: pointer` to the list too? ([Chrome implementation](https://chromium-review.googlesource.com/c/chromium/src/+/1632231)). -- GitHub Notification of comment by hugoholgersson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3395#issuecomment-496498393 using your GitHub account
Received on Tuesday, 28 May 2019 12:37:34 UTC