[mediaqueries] Change how resolution works on non-square pixels

Author: frivoal

mediaqueries/Overview.bs

@@ -1005,21 +1005,14 @@ resolution</h3>
 	Type: range
 	</pre>
 
-	The 'resolution' media feature describes the resolution of the output device,
-	i.e. the density of the pixels,
-	taking into account the <a spec=cssom-view>page zoom</a>
-	but assuming a <a spec=cssom-view>pinch zoom</a> of 1.0.
-
-	When querying devices with non-square pixels,
-	in 'min-resolution' queries the least-dense dimension must be compared to the specified value
-	and in 'max-resolution' queries the most-dense dimensions must be compared instead.
-	A 'resolution' query that's not evaluated in a <a>range context</a> never matches a device with non-square pixels.
-
-	<p class='issue'>
-		Figure out how to make the above work properly for &lt;/&gt; syntax.
-		Just translate it over directly?
-		That prevents you from doing a "less than/greater than" dichotomy without using ''not''.
-		Hmm.
+	The 'resolution' media feature describes the resolution of the output
+	device, i.e. the density of the pixels, taking into account the <a
+	spec=cssom-view>page zoom</a> but assuming a <a spec=cssom-view>pinch zoom</a>
+	of 1.0.
+
+	<p class="note"><<resolution>> does not refer to the number of physical dots physical length units, but to the number of physical dots per CSS unit
+
+	When querying media with non-square pixels, 'resolution' queries the density in the vertical dimension.
 
 	For printers, this corresponds to the screening resolution
 	(the resolution for printing dots of arbitrary color).

mediaqueries/Overview.html

@@ -1422,21 +1422,13 @@ <h3 class="heading settled" data-level=5.1 id=resolution><span class=secno>5.1 <
 
 <table class="definition descdef mq" data-dfn-for=@media><tr><th>Name:<td><dfn class=css data-dfn-for=@media data-dfn-type=descriptor data-export="" id=descdef-media-resolution>resolution<a class=self-link href=#descdef-media-resolution></a></dfn><tr><th>For:<td><a class=css 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 class=prod><a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-values-3/#resolution-value title="<resolution>">&lt;resolution&gt;</a><tr><th>Type:<td>range</table>
 
-<p>The <a class=property data-link-type=propdesc href=#descdef-media-resolution title=resolution>resolution</a> media feature describes the resolution of the output device,
-	i.e. the density of the pixels,
-	taking into account the <a data-link-spec=cssom-view data-link-type=dfn href=http://dev.w3.org/csswg/cssom-view-1/#page-zoom title="page zoom">page zoom</a>
-	but assuming a <a data-link-spec=cssom-view data-link-type=dfn href=http://dev.w3.org/csswg/cssom-view-1/#pinch-zoom title="pinch zoom">pinch zoom</a> of 1.0.</p>
-
-<p>When querying devices with non-square pixels,
-	in <a class=property data-link-type=propdesc title=min-resolution>min-resolution</a> queries the least-dense dimension must be compared to the specified value
-	and in <a class=property data-link-type=propdesc title=max-resolution>max-resolution</a> queries the most-dense dimensions must be compared instead.
-	A <a class=property data-link-type=propdesc href=#descdef-media-resolution title=resolution>resolution</a> query that’s not evaluated in a <a data-link-type=dfn href=#range-context title="range context">range context</a> never matches a device with non-square pixels.</p>
-
-	<p class=issue id=issue-82c28e24><a class=self-link href=#issue-82c28e24></a>
-		Figure out how to make the above work properly for &lt;/&gt; syntax.
-		Just translate it over directly?
-		That prevents you from doing a "less than/greater than" dichotomy without using <a class=css data-link-type=maybe href=#valdef-media-not title=not>not</a>.
-		Hmm.
+<p>The <a class=property data-link-type=propdesc href=#descdef-media-resolution title=resolution>resolution</a> media feature describes the resolution of the output
+	device, i.e. the density of the pixels, taking into account the <a data-link-spec=cssom-view data-link-type=dfn href=http://dev.w3.org/csswg/cssom-view-1/#page-zoom title="page zoom">page zoom</a> but assuming a <a data-link-spec=cssom-view data-link-type=dfn href=http://dev.w3.org/csswg/cssom-view-1/#pinch-zoom title="pinch zoom">pinch zoom</a>
+	of 1.0.</p>
+
+	<p class=note><a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-values-3/#resolution-value title="<resolution>">&lt;resolution&gt;</a> does not refer to the number of physical dots physical length units, but to the number of physical dots per CSS unit
+
+<p>When querying media with non-square pixels, <a class=property data-link-type=propdesc href=#descdef-media-resolution title=resolution>resolution</a> queries the density in the vertical dimension.</p>
 
 <p>For printers, this corresponds to the screening resolution
 	(the resolution for printing dots of arbitrary color).
@@ -2592,12 +2584,6 @@ <h2 class="no-num no-ref heading settled" id=property-index><span class=content>
 
 
 <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>
-		Figure out how to make the above work properly for &lt;/&gt; syntax.
-		Just translate it over directly?
-		That prevents you from doing a "less than/greater than" dichotomy without using <a class=css data-link-type=maybe href=#valdef-media-not title=not>not</a>.
-		Hmm.
-
-<a href=#issue-82c28e24> ↵ </a></div><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-7ddcf400> ↵ </a></div><div class=issue>“Viewport” isn’t the right term here, or in <a class=property data-link-type=propdesc href=#descdef-media-overflow-inline title=overflow-inline>overflow-inline</a>.<a href=#issue-379b3dad> ↵ </a></div><div class=issue>The names of <a class=property data-link-type=propdesc href=#descdef-media-overflow-block title=overflow-block>overflow-block</a> and <a class=property data-link-type=propdesc href=#descdef-media-overflow-inline title=overflow-inline>overflow-inline</a> are possibly confusing.