Re: [csswg-drafts] [mediaqueries-4] any-hover can't be used to detect mixed hover and non-hover capable pointers

scenario here would be for instance: laptop with a touchscreen. primary input is the trackpad/mouse (`hover:hover`). the touchscreen is not hover capable. currently authors cannot detect that beyond the primary input which is hover capable there is also a non-hover capable pointer input (the touchscreen). they can decide "ok, since `hover:hover` is true, i'm good to rely on hover. which works fine ("for the majority of the time", if we take the primary pointer to be indeed the one used most frequently), but as soon as the user does switch to using the touchscreen, things will not work, forcing the user to revert back to using the trackpad/mouse.

with the proposed change, authors would be able to see that yes, while `hover:hover` is true, `any-hover:none` is also true. that then leaves authors the ability to say "ok, even though i could just rely on hover-based stuff for the majority of the time, there may well be cases where the user switches to whatever non-hover-capable pointer input the browser also detected...maybe i should cater for this scenario too". they don't have to, but if they do want to, they can detect this situation too (what they then do is up to them...whether they decide to forego all hover-based stuff on the offchance that the user may switch to the secondary pointer, or whether they load in additional styles/show additional controls/load new scripts to make sure non-hover-capable pointers can also be used...that's up to them)

-- 
GitHub Notification of comment by patrickhlauke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/841#issuecomment-292459100 using your GitHub account

Received on Friday, 7 April 2017 07:07:45 UTC