- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 Nov 2017 20:26:16 +0000
- To: public-css-archive@w3.org
@darktears > Historically any-hover:none would match in the case of a laptop with touchscreen and keyboard (because the touch screen doesn't have hover capabilities). We read literally the "union of capabilities" and maybe the spec wasn't very detailed at the time of implementation. That said thanks for the change and the clarification. Do you mean you ignored the trackpad (assuming the laptop scenario had one)? Or do you mean that both `any-hover:none` (for the touchscreen) and `any-hover:hover` (for the trackpad) evaluated to true? From discussion in https://github.com/w3c/csswg-drafts/issues/737, I believe the latter was not the intention of the spec at the time - hence my clarification. > I'm assuming that a tablet where a mouse/touchpad is added (through USB/Proprietary connectors like Asus Transformers or Bluetooth) should behave like a touchscreen laptop with touchpad/mouse? Aka any-hover:none should be false when some external input is connected and true when only the touchscreen is available to the user? correct. `any-hover:none` should only evaluate to true if there are NO inputs at all that are hover-capable. so, for instance, a pure touchscreen device like a phone (but if you then pair a bluetooth mouse with the phone and it results in a hover-capable mouse pointer, like on android/windows 10 on mobile, then `any-hover:none` should be false due to the mouse being detected). -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/842#issuecomment-343764793 using your GitHub account
Received on Sunday, 12 November 2017 20:26:17 UTC