[css-font-loading] Specify Worker behavior. Remove corresponding issue.

Author: tabatkins

css-font-loading/Overview.bs

@@ -11,7 +11,7 @@ Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/
 Former Editor: John Daggett, Mozilla, jdaggett@mozilla.com
 Abstract: This CSS module describes events and interfaces used for dynamically loading font resources.
 Link Defaults: css-fonts-3 (descriptor) src
-Ignored Terms: domstring, eventinit, cssfontfacerule, eventtarget, workerglobalscope, document
+Ignored Terms: domstring, eventinit, cssfontfacerule, eventtarget, workerglobalscope, document, canvasproxy
 </pre>
 
 <h2 id="introduction">
@@ -352,10 +352,6 @@ The <code>FontFaceSet</code> Interface</h2>
 	and <dfn attribute for=FontFaceSet>[PendingReadyPromises]</dfn> attributes,
 	all of which are initialized to the empty list.
 
-	<p class="issue">
-		Document the FontFaceSet behavior for Workers.
-		(They start out empty, but can construct fonts or be sent them via postMessage.)
-
 <h3 id='set-modifications'>
 Modifications of normal Set methods</h3>
 
@@ -739,6 +735,15 @@ The <code>FontFaceSource</code> interface</h2>
 	For any font-related operation that takes place within one of these contexts,
 	the <a interface>FontFace</a> objects within the <a>font source</a> are its <dfn>available font faces</dfn>.
 
+<h3 id="fontfacesource-workers">
+Worker FontFaceSources</h3>
+
+	Within a Worker document, the <a>font source</a> is initially empty.
+
+	Note: <a interface>FontFace</a> objects can be constructed and added to it as normal,
+	which affects CSS font-matching within the worker
+	(such as, for example, drawing text into a <a interface>CanvasProxy</a>).
+
 <h3 id="document-font-face-set">
 Interaction with CSS’s ''@font-face'' Rule</h3>
 

css-font-loading/Overview.html

@@ -13,8 +13,8 @@
 </p>
   <h1 class="p-name no-ref" id=title>CSS Font Loading Module Level 3</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>W3C First Public Working Draft,
-    <span class=dt-updated><span class=value-title title=20140310>10 March 2014</span></span></span></h2>
-  <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://www.w3.org/TR/2014/WD-css-font-loading-3-20140310/>http://www.w3.org/TR/2014/WD-css-font-loading-3-20140310/</a><dt>Latest version:<dd><a href=http://w3.org/TR/css-font-loading/>http://w3.org/TR/css-font-loading/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-font-loading/>http://dev.w3.org/csswg/css-font-loading/</a>
+    <span class=dt-updated><span class=value-title title=20140325>25 March 2014</span></span></span></h2>
+  <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://www.w3.org/TR/2014/WD-css-font-loading-3-20140325/>http://www.w3.org/TR/2014/WD-css-font-loading-3-20140325/</a><dt>Latest version:<dd><a href=http://w3.org/TR/css-font-loading/>http://w3.org/TR/css-font-loading/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-font-loading/>http://dev.w3.org/csswg/css-font-loading/</a>
     <dt>Feedback:</dt>
         <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-font-loading%5D%20feedback">www-style@w3.org</a>
             with subject line
@@ -87,7 +87,8 @@ <h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class
 		<li><a href=#font-face-set-css><span class=secno>3.6</span> Interaction with CSS Font Loading and Matching</a></ul>
 	<li><a href=#font-face-source><span class=secno>4</span> The <code>FontFaceSource</code> interface</a>
 		<ul class=toc>
-		<li><a href=#document-font-face-set><span class=secno>4.1</span> Interaction with CSS’s <span class=css data-link-type=maybe title=@font-face>@font-face</span> Rule</a></ul>
+		<li><a href=#fontfacesource-workers><span class=secno>4.1</span> Worker FontFaceSources</a>
+		<li><a href=#document-font-face-set><span class=secno>4.2</span> Interaction with CSS’s <span class=css data-link-type=maybe title=@font-face>@font-face</span> Rule</a></ul>
 	<li><a href=#font-load-event-examples><span class=secno>5</span> API Examples</a>
 	<li><a href=#changes><span class=secno></span>Changes</a>
 		<ul class=toc>
@@ -445,10 +446,6 @@ <h2 class="heading settled heading" data-level=3 id=FontFaceSet-interface><span
 	and <dfn class=idl-code data-dfn-for=FontFaceSet data-dfn-type=attribute data-export="" id=dom-fontfaceset-pendingreadypromises>[PendingReadyPromises]<a class=self-link href=#dom-fontfaceset-pendingreadypromises></a></dfn> attributes,
 	all of which are initialized to the empty list.
 
-	<p class=issue id=issue-094f6719><a class=self-link href=#issue-094f6719></a>
-		Document the FontFaceSet behavior for Workers.
-		(They start out empty, but can construct fonts or be sent them via postMessage.)
-
 <h3 class="heading settled heading" data-level=3.1 id=set-modifications><span class=secno>3.1 </span><span class=content>
 Modifications of normal Set methods</span><a class=self-link href=#set-modifications></a></h3>
 
@@ -822,7 +819,16 @@ <h2 class="heading settled heading" data-level=4 id=font-face-source><span class
 <p>	For any font-related operation that takes place within one of these contexts,
 	the <a class=idl-code data-link-type=interface href=#dom-fontface title=fontface>FontFace</a> objects within the <a data-link-type=dfn href=#font-source title="font source">font source</a> are its <dfn data-dfn-type=dfn data-noexport="" id=available-font-faces>available font faces<a class=self-link href=#available-font-faces></a></dfn>.
 
-<h3 class="heading settled heading" data-level=4.1 id=document-font-face-set><span class=secno>4.1 </span><span class=content>
+<h3 class="heading settled heading" data-level=4.1 id=fontfacesource-workers><span class=secno>4.1 </span><span class=content>
+Worker FontFaceSources</span><a class=self-link href=#fontfacesource-workers></a></h3>
+
+<p>	Within a Worker document, the <a data-link-type=dfn href=#font-source title="font source">font source</a> is initially empty.
+
+<p class=note>	Note: <a class=idl-code data-link-type=interface href=#dom-fontface title=fontface>FontFace</a> objects can be constructed and added to it as normal,
+	which affects CSS font-matching within the worker
+	(such as, for example, drawing text into a <a class=idl-code data-link-type=interface title=canvasproxy>CanvasProxy</a>).
+
+<h3 class="heading settled heading" data-level=4.2 id=document-font-face-set><span class=secno>4.2 </span><span class=content>
 Interaction with CSS’s <a class=css data-link-type=maybe href=http://www.w3.org/TR/css-fonts-3/#at-font-face-rule title=@font-face>@font-face</a> Rule</span><a class=self-link href=#document-font-face-set></a></h3>
 
 <p>	The set entries for a document’s <a data-link-type=dfn href=#font-source title="font source">font source</a>
@@ -1156,10 +1162,6 @@ <h2 class="no-num no-ref heading settled heading" id=property-index><span class=
 
 
 <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>
-		Document the FontFaceSet behavior for Workers.
-		(They start out empty, but can construct fonts or be sent them via postMessage.)
-
-<a href=#issue-094f6719> ↵ </a></div><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.