- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Nov 2016 12:24:41 +0000
- To: public-css-archive@w3.org
> perhaps the features should be more tightly limited/defined to only apply to "pointer inputs" per se I think that with the current way none is defined, the spec does not need to distinguish: * If there are no other input device at all, the presence of an input that cannot hover is treated the same as the absence of any input device, and both `hover` and `any-hover` match `none`. * if there are other input devices, the addition of a device that cannot hover has no impact on the result of the hover / any-hover MQs. In both cases, excluding from consideration the device that cannot hover on the basis that it is not a pointing device would have no impact on the MQ. This distinction would be come meaningful if we were to follow to start allowing `none` and `hover` to match at the same time. If I'm understanding you write, what you're after is the ability to distinguish between the absence of a pointing device, and the presence of a pointing device that cannot hover. In the case of the primary one, we can already do so: `(pointer) and (hover: none)` vs `(pointer: none)`. We can also distinguish using any-* between the complete absence of any pointing device at all, and the presence of one or more pointing devices, none of which is able to hover: `(any-pointer) and (any-hover: none)` vs `(any-pointer: none)`. What we cannot tell apart is when there is one or more pointing devices some of which can hover, and one or more pointing devices, all of which can hover. I have a bit of a hard time imagining what a web page would do with that information. I can sort of imagine wanting more fine grained information, and iterating in javascript through an exhaustive list of input devices, each with detailed information, but as long as you're querying about the combined capabilities of all input devices, I don’t quite see it. Would you be so kind as to give me an example of how one would use that? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/737#issuecomment-262499948 using your GitHub account
Received on Wednesday, 23 November 2016 12:24:48 UTC