[mediaqueries] Name the hover values.

Author: tabatkins

mediaqueries/Overview.html

@@ -720,7 +720,7 @@ <h4 class="heading settled heading" data-level=2.4.2 id=mq-boolean-context><span
 		Only some of the <a data-link-type=dfn href=#media-feature title="media features">media features</a> that accept keywords are meaningful in a <a data-link-type=dfn href=#boolean-context title="boolean context">boolean context</a>.
 
 <p>		For example, <span class=css data-link-type=maybe title=(pointer)>(pointer)</span> is useful,
-		as <a class=property data-link-type=propdesc href=#descdef-pointer title=pointer>pointer</a> has a <a class=css data-link-for=pointer data-link-type=maybe href=#valuedef-none title=none>none</a> value to indicate there’s no pointing device at all on the device.
+		as <a class=property data-link-type=propdesc href=#descdef-pointer title=pointer>pointer</a> has a <a class=css data-link-for=pointer data-link-type=maybe href=#valuedef-none1 title=none>none</a> value to indicate there’s no pointing device at all on the device.
 		On the other hand, <span class=css data-link-type=maybe title=(scan)>(scan)</span> is just always true, as there’s no value that means “false”.
 	</div>
 
@@ -1222,7 +1222,7 @@ <h3 class="heading settled heading" data-level=4.15 id=pointer><span class=secno
 	media query takes the following values:
 
 	<dl data-dfn-for=@media/pointer data-dfn-type=value>
-		<dt><dfn class=css-code data-dfn-for=@media/pointer data-dfn-type=value data-export="" id=valuedef-none>none<a class=self-link href=#valuedef-none></a></dfn>
+		<dt><dfn class=css-code data-dfn-for=@media/pointer data-dfn-type=value data-export="" id=valuedef-none1>none<a class=self-link href=#valuedef-none1></a></dfn>
 		<dd>The input mechanism of the device does not include a pointing device.
 
 		<dt><dfn class=css-code data-dfn-for=@media/pointer data-dfn-type=value data-export="" id=valuedef-coarse>coarse<a class=self-link href=#valuedef-coarse></a></dfn>
@@ -1278,7 +1278,7 @@ <h3 class="heading settled heading" data-level=4.15 id=pointer><span class=secno
 		</div>
 
 <p>	For accessibility reasons, even on devices whose pointing device can be
-	described as <a class=css data-link-type=maybe href=#valuedef-fine title=fine>fine</a>, the UA may give a value of <a class=css data-link-type=maybe href=#valuedef-coarse title=coarse>coarse</a> or <a class=css data-link-for=pointer data-link-type=maybe href=#valuedef-none title=none>none</a> to
+	described as <a class=css data-link-type=maybe href=#valuedef-fine title=fine>fine</a>, the UA may give a value of <a class=css data-link-type=maybe href=#valuedef-coarse title=coarse>coarse</a> or <a class=css data-link-for=pointer data-link-type=maybe href=#valuedef-none1 title=none>none</a> to
 	this media query, to indicate that the user has difficulties
 	manipulating the input device accurately or at all.
 
@@ -1296,24 +1296,50 @@ <h3 class="heading settled heading" data-level=4.15 id=pointer><span class=secno
 <h3 class="heading settled heading" data-level=4.16 id=hover><span class=secno>4.16 </span><span class=content>
 hover</span><a class=self-link href=#hover></a></h3>
 
-<table class="definition descdef mq" data-dfn-for="<a at-rule>@media</a>"><tr><th>Name:<td><dfn class=css-code data-dfn-for="<a at-rule>@media</a>" data-dfn-type=descriptor data-export="" id=descdef-hover>hover<a class=self-link href=#descdef-hover></a></dfn><tr><th>For:<td><a class=css-code data-link-type=at-rule href=http://dev.w3.org/csswg/css-conditional-3/#at-ruledef-media title=@media>@media</a><tr><th>Value:<td><a class="production css-code" data-link-type=type href=#typedef-mq-boolean title="<mq-boolean>">&lt;mq-boolean&gt;</a><tr><th>Type:<td>discrete</table>
+<table class="definition descdef mq" data-dfn-for="<a at-rule>@media</a>"><tr><th>Name:<td><dfn class=css-code data-dfn-for="<a at-rule>@media</a>" data-dfn-type=descriptor data-export="" id=descdef-hover>hover<a class=self-link href=#descdef-hover></a></dfn><tr><th>For:<td><a class=css-code data-link-type=at-rule href=http://dev.w3.org/csswg/css-conditional-3/#at-ruledef-media title=@media>@media</a><tr><th>Value:<td>none | on-demand | over<tr><th>Type:<td>discrete</table>
 <p>	The <a class=property data-link-type=propdesc href=#descdef-hover title=hover>hover</a> media feature is used to query whether primary pointing system
-	used on the output device can hover or not.  If it can, the value will be 1.
-	Otherwise, the value will be 0.
+	used on the output device can hover or not.
+
+	<dl data-dfn-for=@media/hover data-dfn-type=value>
+		<dt><dfn class=css-code data-dfn-for=@media/hover data-dfn-type=value data-export="" id=valuedef-none>none<a class=self-link href=#valuedef-none></a></dfn>
+		<dd>
+			Indicates that the primary pointing system can’t hover,
+			or there is no pointing system.
+
+		<dt><dfn class=css-code data-dfn-for=@media/hover data-dfn-type=value data-export="" id=valuedef-on-demand>on-demand<a class=self-link href=#valuedef-on-demand></a></dfn>
+		<dd>
+			Indicates that the primary pointing system can hover,
+			but it requires a significant action on the user’s part.
+			For example, some devices can’t normally hover,
+			but will activate hover on a “long press”.
+
+		<dt><dfn class=css-code data-dfn-for=@media/hover data-dfn-type=value data-export="" id=valuedef-over>over<a class=self-link href=#valuedef-over></a></dfn>
+		<dd>
+			Indicates that the primary pointing system can easily hover over parts of the page.
+	</dl>
 
 <p>	If a device has multiple pointing devices, some of which support hovering
 	and some of which not, it is  recommended that the UA reports the hovering
 	ability of the least capable of the primary pointing devices.
 
-<p class=note>	Note: The value of the <a class=property data-link-type=propdesc href=#descdef-hover title=hover>hover</a> media feature should for example be 0 on a touch screen
-	device that can also be controlled via an optional mouse. Authors should
-	therefore be careful not to assume that the ':hover' pseudo class will never
-	match on device where 'hover:0' is true, but they should design layouts
-	that do not depend on hovering to be fully usable.
+	<div class=example>
+		For example, on a touch screen device that can also be controlled by an optional mouse,
+		the <a class=property data-link-type=propdesc href=#descdef-hover title=hover>hover</a> <a data-link-type=dfn href=#media-feature title="media feature">media feature</a> should match <a class=css data-link-for=hover data-link-type=maybe href=#valuedef-none title=none>none</a>,
+		as the primary interaction mode (touching the screen) can’t hover.
+
+<p>		Authors should therefore be careful not to assume that the ':hover' pseudo class
+		will never match on device where 'hover:none' is true,
+		but they should design layouts that do not depend on hovering to be fully usable.
+	</div>
+
+	<p class=issue id=issue-d8ce9763><a class=self-link href=#issue-d8ce9763></a>
+		Rob Coulburn points out that Mac devices turn off scrollbars when you plug in a mouse,
+		which means that it *does* react to changing input devices.
+		But is this just because it considers a plugged-in mouse to be "primary"?
 
 <p>	For accessibility reasons, even on devices that do support hovering,
-	the UA may give a value of 0 to this media query, to opt into layouts that work
-	well without hovering.
+	the UA may give a value of <a class=css data-link-type=propdesc href=#descdef-hover title=hover>hover: none</a> to this media query,
+	to opt into layouts that work well without hovering.
 
 	<div class=example>
 		<pre>/* Only use a hover-activated drop down menu on devices that can hover. */
@@ -1612,11 +1638,14 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>monochrome, <a href=#descdef-monochrome title="section 4.10">4.10</a>
 <li>&lt;mq-boolean&gt;, <a href=#typedef-mq-boolean title="section 1.2">1.2</a>
 <li>none<ul><li>value for @media/script, <a href=#valuedef-none0 title="section 4.14">4.14</a>
-<li>value for @media/pointer, <a href=#valuedef-none title="section 4.15">4.15</a>
+<li>value for @media/pointer, <a href=#valuedef-none1 title="section 4.15">4.15</a>
+<li>value for @media/hover, <a href=#valuedef-none title="section 4.16">4.16</a>
 </ul><li>normal, <a href=#valuedef-normal title="section 4.17">4.17</a>
 <li>not, <a href=#valuedef-not title="section 2.2.1">2.2.1</a>
+<li>on-demand, <a href=#valuedef-on-demand title="section 4.16">4.16</a>
 <li>only, <a href=#valuedef-only title="section 2.2.2">2.2.2</a>
 <li>orientation, <a href=#descdef-orientation title="section 4.5">4.5</a>
+<li>over, <a href=#valuedef-over title="section 4.16">4.16</a>
 <li>pointer, <a href=#descdef-pointer title="section 4.15">4.15</a>
 <li>print, <a href=#valuedef-print title="section 2.3">2.3</a>
 <li>projection, <a href=#valuedef-projection title="section 2.3">2.3</a>
@@ -1650,14 +1679,19 @@ <h2 class="no-num no-ref heading settled heading" id=property-index><span class=
 <tr><th scope-row=""><a data-property="">grid</a><td>&lt;mq-boolean&gt;<td><td>discrete
 <tr><th scope-row=""><a data-property="">script</a><td>none | enabled<td><td>discrete
 <tr><th scope-row=""><a data-property="">pointer</a><td>none | coarse | fine<td><td>discrete
-<tr><th scope-row=""><a data-property="">hover</a><td>&lt;mq-boolean&gt;<td><td>discrete
+<tr><th scope-row=""><a data-property="">hover</a><td>none | on-demand | over<td><td>discrete
 <tr><th scope-row=""><a data-property="">luminosity</a><td>dim | normal | washed<td><td>discrete</table></div>
 
 
 <h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue>
 		Another media feature should probably be added to deal with the type of resolution authors want to know to deal with monochrome printing.
 
 	<a href=#issue-f5f73c8d> ↵ </a></div><div class=issue>
+		Rob Coulburn points out that Mac devices turn off scrollbars when you plug in a mouse,
+		which means that it *does* react to changing input devices.
+		But is this just because it considers a plugged-in mouse to be "primary"?
+
+<a href=#issue-d8ce9763> ↵ </a></div><div class=issue>
 		Using this media feature for accessibility purposes overlaps
 		a lot with the high-contrast media feature proposed by Microsoft:
 		<a href=http://msdn.microsoft.com/en-us/library/windows/apps/hh465764.aspx>http://msdn.microsoft.com/en-us/library/windows/apps/hh465764.aspx</a>.

mediaqueries/Overview.src.html

@@ -1192,34 +1192,60 @@ <h3 id="hover">
 
 	<pre class='descdef mq'>
 	Name: hover
-	Value: <<mq-boolean>>
+	Value: none | on-demand | over
 	For: @media
 	Type: discrete
 	</pre>
 
 	The 'hover' media feature is used to query whether primary pointing system
-	used on the output device can hover or not.  If it can, the value will be 1.
-	Otherwise, the value will be 0.
+	used on the output device can hover or not.
+
+	<dl dfn-type=value dfn-for="@media/hover">
+		<dt><dfn>none</dfn>
+		<dd>
+			Indicates that the primary pointing system can't hover,
+			or there is no pointing system.
+
+		<dt><dfn>on-demand</dfn>
+		<dd>
+			Indicates that the primary pointing system can hover,
+			but it requires a significant action on the user's part.
+			For example, some devices can't normally hover,
+			but will activate hover on a “long press”.
+
+		<dt><dfn>over</dfn>
+		<dd>
+			Indicates that the primary pointing system can easily hover over parts of the page.
+	</dl>
 
 	If a device has multiple pointing devices, some of which support hovering
 	and some of which not, it is  recommended that the UA reports the hovering
 	ability of the least capable of the primary pointing devices.
 
-	Note: The value of the 'hover' media feature should for example be 0 on a touch screen
-	device that can also be controlled via an optional mouse. Authors should
-	therefore be careful not to assume that the ':hover' pseudo class will never
-	match on device where 'hover:0' is true, but they should design layouts
-	that do not depend on hovering to be fully usable.
+	<div class='example'>
+		For example, on a touch screen device that can also be controlled by an optional mouse,
+		the 'hover' <a>media feature</a> should match ''hover/none'',
+		as the primary interaction mode (touching the screen) can't hover.
+
+		Authors should therefore be careful not to assume that the ':hover' pseudo class
+		will never match on device where 'hover:none' is true,
+		but they should design layouts that do not depend on hovering to be fully usable.
+	</div>
+
+	<p class='issue'>
+		Rob Coulburn points out that Mac devices turn off scrollbars when you plug in a mouse,
+		which means that it *does* react to changing input devices.
+		But is this just because it considers a plugged-in mouse to be "primary"?
 
 	For accessibility reasons, even on devices that do support hovering,
-	the UA may give a value of 0 to this media query, to opt into layouts that work
-	well without hovering.
+	the UA may give a value of ''hover: none'' to this media query,
+	to opt into layouts that work well without hovering.
 
 	<div class="example">
 		<pre>
 		/* Only use a hover-activated drop down menu on devices that can hover. */
 		@media (hover) {
-			.menu &gt; li        {display:inline-block;}
+			.menu > li        {display:inline-block;}
 			.menu ul          {display:none; position:absolute;}
 			.menu li:hover ul {display:block; list-style:none; padding:0;}
 			/* ... */