- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Apr 2017 07:00:20 +0000
- To: public-css-archive@w3.org
because if you aknowledge that the "offer hover as a convenience" scenario is a valid one, then authors should be able to base that decision both when the primary is not hover capable, or if at least one of the secondary inputs is not hover capable (and with the proposed change they can also differentiate the two of course, based on the value of the primary `hover:...`). you could argue "but once authors know the primary is/isn't hover capable, that's all they need", but that still gives undue prominence to what the primary pointer does. authors can of course choose to just go mainly by what the primary does, but this allows them some additional granularity in how they base their final decision. -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/841#issuecomment-292457845 using your GitHub account
Received on Friday, 7 April 2017 07:00:31 UTC