From ba0adc4ed8540dcf34651e75192f9846b7182d71 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Sat, 19 Nov 2016 11:02:50 +0100 Subject: [PATCH 1/3] Add pointer:none examples, expand stylus examples - add classic `pointer: none` inputs - preferred term is digitizers, rather than screens (e.g. Wacom are external devices, not screens) - advanced stylus digitizers can sense a hovering stylus, and do trigger hover interactions - split out basic and advanced stylus - removed the `` ... appears to serve no actual (styling?) purpose --- mediaqueries/Overview.bs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mediaqueries/Overview.bs b/mediaqueries/Overview.bs index 47555186bc6..2d4e98c17d4 100644 --- a/mediaqueries/Overview.bs +++ b/mediaqueries/Overview.bs @@ -1571,23 +1571,23 @@ Interaction Media Features Typical examples of devices matching combinations of 'pointer' and 'hover': - - -
+ ''pointer: none'' ''pointer: coarse'' ''pointer: fine''
''hover: none'' + keyboard-only controls, sequential/spatial (d-pad) focus navigation smartphones, touch screens - stylus-based screens (Cintiq, Wacom, etc) + basic stylus digitizers (Cintiq, Wacom, etc)
''hover: hover'' + Nintendo Wii controller, Kinect - mouse, touch pad + mouse, touch pad, advanced stylus digitizers (Surface, Samsung Note, Wacom Intuos Pro, etc)
+ The 'pointer' and 'hover' features relate to the characteristics of the “primary” input mechanism, while 'any-pointer' and 'any-hover' can be used to query the properties of all potentially available input mechanisms. + +
+ While this specification does not define how User Agents should decide what the “primary” input is, the expectation is that User Agents should make this determination by combining knowledge about the device/environment they are running on, the number and type of input mechanisms available, and a notion of which of these inputs is generally and/or currently being used. User Agents may also decide to dynamically change what type of input is deemed to be primary, in response to changes in the user environment or in the way the user is interacting with the UA. +
+

Pointing Device Quality: the 'pointer' feature

From 071e1323607008851c9d06ee5b719f18d6a3de02 Mon Sep 17 00:00:00 2001 From: Tab Atkins Jr Date: Tue, 22 Nov 2016 10:09:05 -0800 Subject: [PATCH 3/3] fix linewrapping --- mediaqueries/Overview.bs | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/mediaqueries/Overview.bs b/mediaqueries/Overview.bs index ef15972f2f1..f3ffcb53b75 100644 --- a/mediaqueries/Overview.bs +++ b/mediaqueries/Overview.bs @@ -1597,11 +1597,17 @@ Interaction Media Features - The 'pointer' and 'hover' features relate to the characteristics of the “primary” input mechanism, while 'any-pointer' and 'any-hover' can be used to query the properties of all potentially available input mechanisms. - -
- While this specification does not define how User Agents should decide what the “primary” input is, the expectation is that User Agents should make this determination by combining knowledge about the device/environment they are running on, the number and type of input mechanisms available, and a notion of which of these inputs is generally and/or currently being used. User Agents may also decide to dynamically change what type of input is deemed to be primary, in response to changes in the user environment or in the way the user is interacting with the UA. -
+ The 'pointer' and 'hover' features relate to the characteristics of the “primary” input mechanism, + while 'any-pointer' and 'any-hover' can be used to query the properties of all potentially available input mechanisms. + + Note: While this specification does not define how User Agents should decide what the “primary” input is, + the expectation is that User Agents should make this determination + by combining knowledge about the device/environment they are running on, + the number and type of input mechanisms available, + and a notion of which of these inputs is generally and/or currently being used. + User Agents may also decide to dynamically change what type of input is deemed to be primary, + in response to changes in the user environment + or in the way the user is interacting with the UA.

Pointing Device Quality: the 'pointer' feature