[mediaqueries] Close the issues resolved at the F2F to not need changes

Author: frivoal

mediaqueries/Overview.bs

@@ -102,10 +102,6 @@ Values</h3>
 	<<ratio>>s can be ordered or compared by transforming them into the number
 	obtained by dividing their first <<integer>> by their second <<integer>>.
 
-	<p class='issue'>
-		Reasonable to restrict <<ratio>> to <<integer>>s?
-		I've seen aspect ratios written with decimal points in real life.
-
 	The <dfn type>&lt;mq-boolean></dfn> value type is an <<integer>>
 	with the value ''0'' or ''1''.
 	Any other integer value is invalid.
@@ -1806,9 +1802,6 @@ scripting</h3>
 
 	Note: A future level of CSS may extend this media feature to allow fine-grained detection of which script is allowed to run.
 
-	<p class='issue'>
-		Is there a use-case for distinguishing between "UA doesn't support scripting" and "scripting is supported, but turned off"?
-
 <!--
 ████  ██████   ██████  ██     ██ ████████  ██████
  ██  ██    ██ ██    ██ ██     ██ ██       ██    ██
@@ -1860,11 +1853,6 @@ Assorted Issues</h2>
 		MQ for detecting if the device is willing to display/print backgrounds and other ink-hungry properties.
 	</div>
 
-	<div class='issue'>
-		What to do about the 'view-mode' media feature?
-	</div>
-
-
 <!--
  ██████  ██     ██  ██████  ████████  ███████  ██     ██       ██     ██  ███████
 ██    ██ ██     ██ ██    ██    ██    ██     ██ ███   ███       ███   ███ ██     ██

mediaqueries/Overview.html

@@ -289,10 +289,6 @@ <h3 class="heading settled" data-level=1.2 id=values><span class=secno>1.2 </spa
 	<a class="production css" data-link-type=type href=#typedef-ratio title="<ratio>">&lt;ratio&gt;</a>s can be ordered or compared by transforming them into the number
 	obtained by dividing their first <a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-syntax-3/#typedef-integer title="<integer>">&lt;integer&gt;</a> by their second <a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-syntax-3/#typedef-integer title="<integer>">&lt;integer&gt;</a>.</p>
 
-	<p class=issue id=issue-2ae5b8ca><a class=self-link href=#issue-2ae5b8ca></a>
-		Reasonable to restrict <a class="production css" data-link-type=type href=#typedef-ratio title="<ratio>">&lt;ratio&gt;</a> to <a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-syntax-3/#typedef-integer title="<integer>">&lt;integer&gt;</a>s?
-		I’ve seen aspect ratios written with decimal points in real life.
-
 <p>The <dfn class=css data-dfn-type=type data-export="" id=typedef-mq-boolean>&lt;mq-boolean&gt;<a class=self-link href=#typedef-mq-boolean></a></dfn> value type is an <a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-syntax-3/#typedef-integer title="<integer>">&lt;integer&gt;</a>
 	with the value <span class=css>0</span> or <span class=css>1</span>.
 	Any other integer value is invalid.
@@ -2092,9 +2088,6 @@ <h3 class="heading settled" data-level=9.1 id=scripting><span class=secno>9.1 </
 
 <p class=note>Note: A future level of CSS may extend this media feature to allow fine-grained detection of which script is allowed to run.</p>
 
-	<p class=issue id=issue-a835c36c><a class=self-link href=#issue-a835c36c></a>
-		Is there a use-case for distinguishing between "UA doesn’t support scripting" and "scripting is supported, but turned off"?
-
 
 
 <h2 class="heading settled" data-level=10 id=assorted-issues><span class=secno>10 </span><span class=content>
@@ -2138,11 +2131,6 @@ <h2 class="heading settled" data-level=10 id=assorted-issues><span class=secno>1
 <p>MQ for detecting if the device is willing to display/print backgrounds and other ink-hungry properties.</p>
 	</div>
 
-	<div class=issue id=issue-303868dc><a class=self-link href=#issue-303868dc></a>
-		What to do about the <a class=property data-link-type=propdesc title=view-mode>view-mode</a> media feature?
-	</div>
-
-
 
 
 <h2 class="heading settled" data-level=11 id=custom-mq><span class=secno>11 </span><span class=content>
@@ -2592,10 +2580,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>
-		Reasonable to restrict <a class="production css" data-link-type=type href=#typedef-ratio title="<ratio>">&lt;ratio&gt;</a> to <a class="production css" data-link-type=type href=http://dev.w3.org/csswg/css-syntax-3/#typedef-integer title="<integer>">&lt;integer&gt;</a>s?
-		I’ve seen aspect ratios written with decimal points in real life.
-
-<a href=#issue-2ae5b8ca> ↵ </a></div><div class=issue>
 		We should deprecate the device-* media features.
 		They don’t do anything useful,
 		and are mostly just abused as a ghetto "phone versus desktop" media type.
@@ -2618,11 +2602,6 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 		as discussed in http://lists.w3.org/Archives/Public/www-style/2013Oct/0672.html
 
 	<a href=#issue-4da6b7f1> ↵ </a></div><div class=issue>
-		Is there a use-case for distinguishing between "UA doesn’t support scripting" and "scripting is supported, but turned off"?
-
-
-
-<a href=#issue-a835c36c> ↵ </a></div><div class=issue>
 		We need a media feature (or set of media features) to detect the type of keyboard available.
 		It should be able to distinguish between full computer keyboards, phone dial pads, tv remotes, or virtual keyboards.
 		As an attempt at an exhaustive list is likely to fail,
@@ -2655,8 +2634,6 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 
 <p>MQ for detecting if the device is willing to display/print backgrounds and other ink-hungry properties.</p>
 	<a href=#issue-c2124305> ↵ </a></div><div class=issue>
-		What to do about the <a class=property data-link-type=propdesc title=view-mode>view-mode</a> media feature?
-	<a href=#issue-303868dc> ↵ </a></div><div class=issue>
 		Define a map of names to values for JS.
 		Values can be either a MediaQueryList object or a boolean,
 		in which case it’s treated identically to the above,