- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Apr 2017 06:52:30 +0000
- To: public-css-archive@w3.org
> Thanks to the primary / non primary distinction, you can already know that the normal way of interacting with the device is hover-incapable, but that the user may have additional means of hovering at their disposition. So you know that you should not depend on hovering for essential functions(hover:none), but that if you offer additional conveniences based on hover, the user may take advantage of them (any-hover:hover). What can you do differently with the additional bit of information you're proposing? with the proposed change, you can detect the opposite situation that may lead you to the same decision. the primary being hover capable (`hover:hover`), but that other inputs the user may use are not (proposed `any-hover:none`), which can lead you to the same decision - not to rely completely on hover-based interactions, because the user may well be using/switch to using one of the other pointer-based inputs, so perhaps (even though the primary is hover capable) treat it as a convenience. -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/841#issuecomment-292456538 using your GitHub account
Received on Friday, 7 April 2017 06:52:36 UTC