- From: Alexis Menard via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2017 03:49:26 +0000
- To: public-css-archive@w3.org
I would like to mention for posterity that this change had a potential compat impact on Chrome. 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. Interaction MQ are truly dynamic in Chrome since recently : we react to the best we can to input capabilities changes from the OS. Think the case of convertible/detachable laptops where the touchpad is gone/deactivated. With that said just to clarify, I'm assuming that a tablet where a mouse/touchpad is added (through USB/Proprietary connectors like Pixel 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? I'm aligning the implementation with the spec as we speak. -- GitHub Notification of comment by darktears Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/842#issuecomment-343039560 using your GitHub account
Received on Thursday, 9 November 2017 03:49:28 UTC