[css-font-loading] Turn local font issue into a note about planned future behavior.

Author: tabatkins

css-font-loading/Overview.bs

@@ -760,13 +760,8 @@ Interaction with CSS’s ''@font-face'' Rule</h3>
 	All non-<a>CSS-connected</a> <a interface>FontFace</a> objects must be sorted after the <a>CSS-connected</a> ones,
 	in insertion order.
 
-	<p class='issue'>
-		Can/should we include the local system fonts,
-		or is that a fingerprinting problem?
-		I think the set of local fonts is trivially discoverable anyway.
-		Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
-		and perhaps can be queried against?
-		This would make FontFaceSet fully explain the current behavior of fonts.
+	Note: It is expected that a future version of this specification
+	will define ways of interacting with and querying local fonts as well.
 
 <h2 id="font-load-event-examples">
 API Examples</h2>

css-font-loading/Overview.html

@@ -106,8 +106,7 @@ <h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class
 		<li><a href=#normative><span class=secno></span> Normative References</a>
 		<li><a href=#informative><span class=secno></span> Informative References</a></ul>
 	<li><a href=#index><span class=secno></span> Index</a>
-	<li><a href=#property-index><span class=secno></span> Property index</a>
-	<li><a href=#issues-index><span class=secno></span>Issues Index</a></ul></div>
+	<li><a href=#property-index><span class=secno></span> Property index</a></ul></div>
 
 
 
@@ -844,13 +843,8 @@ <h3 class="heading settled heading" data-level=4.2 id=document-font-face-set><sp
 <p>	All non-<a data-link-type=dfn href=#css-connected title=css-connected>CSS-connected</a> <a class=idl-code data-link-type=interface href=#dom-fontface title=fontface>FontFace</a> objects must be sorted after the <a data-link-type=dfn href=#css-connected title=css-connected>CSS-connected</a> ones,
 	in insertion order.
 
-	<p class=issue id=issue-d3a24efa><a class=self-link href=#issue-d3a24efa></a>
-		Can/should we include the local system fonts,
-		or is that a fingerprinting problem?
-		I think the set of local fonts is trivially discoverable anyway.
-		Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
-		and perhaps can be queried against?
-		This would make FontFaceSet fully explain the current behavior of fonts.
+<p class=note>	Note: It is expected that a future version of this specification
+	will define ways of interacting with and querying local fonts as well.
 
 <h2 class="heading settled heading" data-level=5 id=font-load-event-examples><span class=secno>5 </span><span class=content>
 API Examples</span><a class=self-link href=#font-load-event-examples></a></h2>
@@ -1161,12 +1155,3 @@ <h2 class="no-num no-ref heading settled heading" id=property-index><span class=
 <div data-fill-with=property-index><p>No properties defined.</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>
-		Can/should we include the local system fonts,
-		or is that a fingerprinting problem?
-		I think the set of local fonts is trivially discoverable anyway.
-		Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
-		and perhaps can be queried against?
-		This would make FontFaceSet fully explain the current behavior of fonts.
-
-<a href=#issue-d3a24efa> ↵ </a></div></div>