[mediaqueries] Remove issue about Mac devices reacting to mouse being plugged in.

Author: tabatkins

mediaqueries/Overview.html

@@ -1739,11 +1739,6 @@ <h3 class="heading settled heading" data-level=7.2 id=hover><span class=secno>7.
 		but they should design layouts that do not depend on hovering to be fully usable.
 	</div>
 
-	<p class=issue id=issue-4e5f4bb5><a class=self-link href=#issue-4e5f4bb5></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 <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.
@@ -2228,11 +2223,6 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 		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>
-		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-4e5f4bb5> ↵ </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

@@ -1422,11 +1422,6 @@ <h3 id="hover">
 		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 ''hover: none'' to this media query,
 	to opt into layouts that work well without hovering.