- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Nov 2016 09:22:09 +0000
- To: public-css-archive@w3.org
True, keyboard on desktop would be the fly in the ointment (unless UAs were using some heuristics - similar to what Firefox does with regards to `::moz-focusring` where it only considers keyboard if the user interacted with the page at least once using, say, TAB/SHIFT+TAB). Incidentally, authors *should* already be considering the desktop/keyboard use case anyway for accessibility reasons today... Related musing: perhaps the features should be more tightly limited/defined to only apply to "pointer inputs" per se - similar to what happens with Pointer Events (I originally argued, but then conceded, that keyboard should also be a `pointerType` back before PE Level 1 went to TR). As for the reductio ad absurdum case, it doesn't seem too absurd to me - if the user does add an input that doesn't hover and doesn't have a traditional pointer, then yes I would expect the query (if it were modified as per this PR) to then return true for `(any-pointer: none)` and `(any-hover: none)`, as that would be the truthful answer to the question "are there any inputs now present which don't have a pointer and aren't hover capable?" -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/737#issuecomment-262465490 using your GitHub account
Received on Wednesday, 23 November 2016 09:22:15 UTC