[css-font-load-events] Add to the local fonts issue.

Author: tabatkins

css-font-load-events/Overview.html

@@ -77,7 +77,7 @@
 </a></p>
   <h1 class="p-name no-ref" id=title>CSS Font Load Events Module Level 3</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
-    <span class=dt-updated><span class=value-title title=20130917>17 September 2013</span></span></span></h2>
+    <span class=dt-updated><span class=value-title title=20130930>30 September 2013</span></span></span></h2>
   <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://dev.w3.org/csswg/css-font-load-events/>http://dev.w3.org/csswg/css-font-load-events/</a><dt>Latest version:<dd><a href=http://www.w3.org/TR/css-font-load-events-3/>http://www.w3.org/TR/css-font-load-events-3/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-font-load-events/>http://dev.w3.org/csswg/css-font-load-events/</a>
 <dt>Feedback:</dt>
     <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-font-load-events%5D%20feedback">www-style@w3.org</a>
@@ -178,12 +178,12 @@ <h2 class="heading settled heading" data-level=2 id=fontface-interface><span cla
 	<pre class=idl>typedef (<a data-link-type=idl title=arraybuffer>ArrayBuffer</a> or <a data-link-type=idl title=arraybufferview>ArrayBufferView</a>) <dfn class=idl-code data-dfn-type=typedef data-export="" id=typedefdef-binarydata title=BinaryData>BinaryData<a class=self-link href=#typedefdef-binarydata></a></dfn>;
 
   dictionary <dfn class=idl-code data-dfn-type=dictionary data-export="" id=dictdef-fontfacedescriptors title=FontFaceDescriptors>FontFaceDescriptors<a class=self-link href=#dictdef-fontfacedescriptors></a></dfn> {
-    DOMString style = "normal";
-    DOMString weight = "normal";
-    DOMString stretch = "normal";
-    DOMString unicodeRange = "U+0-10FFFF";
-    DOMString variant = "normal";
-    DOMString featureSettings = "normal";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-style title=style>style<a class=self-link href=#dom-fontfacedescriptors-style></a></dfn> = "normal";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-weight title=weight>weight<a class=self-link href=#dom-fontfacedescriptors-weight></a></dfn> = "normal";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-stretch title=stretch>stretch<a class=self-link href=#dom-fontfacedescriptors-stretch></a></dfn> = "normal";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-unicoderange title=unicodeRange>unicodeRange<a class=self-link href=#dom-fontfacedescriptors-unicoderange></a></dfn> = "U+0-10FFFF";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-variant title=variant>variant<a class=self-link href=#dom-fontfacedescriptors-variant></a></dfn> = "normal";
+    DOMString <dfn class=idl-code data-dfn-for=FontFaceDescriptors data-dfn-type=dict-member data-export="" id=dom-fontfacedescriptors-featuresettings title=featureSettings>featureSettings<a class=self-link href=#dom-fontfacedescriptors-featuresettings></a></dfn> = "normal";
   };
 
   enum <dfn class=idl-code data-dfn-type=enum data-export="" id=enumdef-fontfaceloadstatus title=FontFaceLoadStatus>FontFaceLoadStatus<a class=self-link href=#enumdef-fontfaceloadstatus></a></dfn> { "unloaded", "loading", "loaded", "error" };
@@ -416,7 +416,7 @@ <h2 class="heading settled heading" data-level=3 id=FontFaceSet-interface><span
 The <code>FontFaceSet</code> Interface</span><a class=self-link href=#FontFaceSet-interface></a></h2>
 
 	<pre class=idl>dictionary <dfn class=idl-code data-dfn-type=dictionary data-export="" id=dictdef-cssfontfaceloadeventinit title=CSSFontFaceLoadEventInit>CSSFontFaceLoadEventInit<a class=self-link href=#dictdef-cssfontfaceloadeventinit></a></dfn> : <a data-link-type=idl title=eventinit>EventInit</a> {
-    sequence&lt;<a data-link-type=idl title=cssfontfacerule>CSSFontFaceRule</a>&gt; fontfaces = null;
+    sequence&lt;<a data-link-type=idl title=cssfontfacerule>CSSFontFaceRule</a>&gt; <dfn class=idl-code data-dfn-for=CSSFontFaceLoadEventInit data-dfn-type=dict-member data-export="" id=dom-cssfontfaceloadeventinit-fontfaces title=fontfaces>fontfaces<a class=self-link href=#dom-cssfontfaceloadeventinit-fontfaces></a></dfn> = null;
   };
 
   [Constructor(DOMString <dfn class=idl-code data-dfn-for=CSSFontFaceLoadEvent/CSSFontFaceLoadEvent() data-dfn-type=argument data-export="" id=dom-cssfontfaceloadeventcssfontfaceloadevent-type title=type>type<a class=self-link href=#dom-cssfontfaceloadeventcssfontfaceloadevent-type></a></dfn>, optional <a data-link-type=idl href=#dictdef-cssfontfaceloadeventinit title=cssfontfaceloadeventinit>CSSFontFaceLoadEventInit</a> <dfn class=idl-code data-dfn-for=CSSFontFaceLoadEvent/CSSFontFaceLoadEvent() data-dfn-type=argument data-export="" id=dom-cssfontfaceloadeventcssfontfaceloadevent-eventinitdict title=eventInitDict>eventInitDict<a class=self-link href=#dom-cssfontfaceloadeventcssfontfaceloadevent-eventinitdict></a></dfn>)]
@@ -837,10 +837,13 @@ <h3 class="heading settled heading" data-level=4.1 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-28c4f329><a class=self-link href=#issue-28c4f329></a>
+	<p class=issue id=issue-86d79dbc><a class=self-link href=#issue-86d79dbc></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
+		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.
 
 <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>
@@ -1087,6 +1090,7 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>[[FailedFonts]], <a href=#dom-fontfaceset-failedfonts title="section 3">3</a>
 <li>family, <a href=#dom-fontface-family title="section 2">2</a>
 <li>family, <a href=#dom-fontfacefontface-fontface-family title="section 2.1">2.1</a>
+<li>featureSettings, <a href=#dom-fontfacedescriptors-featuresettings title="section 2">2</a>
 <li>featureSettings, <a href=#dom-fontface-featuresettings title="section 2">2</a>
 <li>fire a font load event, <a href=#fire-a-font-load-event title="section 3.2">3.2</a>
 <li>font, <a href=#dom-fontfacesetmatch-match-font title="section 3.3">3.3</a>
@@ -1096,6 +1100,7 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>FontFace(), <a href=#dom-fontface-fontface title="section 2.1">2.1</a>
 <li>FontFaceDescriptors, <a href=#dictdef-fontfacedescriptors title="section 2">2</a>
 <li>FontFaceLoadStatus, <a href=#enumdef-fontfaceloadstatus title="section 2">2</a>
+<li>fontfaces, <a href=#dom-cssfontfaceloadeventinit-fontfaces title="section 3">3</a>
 <li>fontfaces, <a href=#dom-cssfontfaceloadevent-fontfaces title="section 3">3</a>
 <li>FontFaceSet, <a href=#dom-fontfaceset title="section 3">3</a>
 <li>FontFaceSetLoadStatus, <a href=#enumdef-fontfacesetloadstatus title="section 3">3</a>
@@ -1123,15 +1128,20 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>source, <a href=#dom-fontfacefontface-fontface-source title="section 2.1">2.1</a>
 <li>status, <a href=#dom-fontface-status title="section 2">2</a>
 <li>status, <a href=#dom-fontfaceset-status title="section 3">3</a>
+<li>stretch, <a href=#dom-fontfacedescriptors-stretch title="section 2">2</a>
 <li>stretch, <a href=#dom-fontface-stretch title="section 2">2</a>
+<li>style, <a href=#dom-fontfacedescriptors-style title="section 2">2</a>
 <li>style, <a href=#dom-fontface-style title="section 2">2</a>
 <li>text, <a href=#dom-fontfacesetmatch-match-text title="section 3.3">3.3</a>
 <li>text, <a href=#dom-fontfacesetload-load-text title="section 3.4">3.4</a>
 <li>text, <a href=#dom-fontfacesetcheck-check-text title="section 3.5">3.5</a>
 <li>type, <a href=#dom-cssfontfaceloadeventcssfontfaceloadevent-type title="section 3">3</a>
+<li>unicodeRange, <a href=#dom-fontfacedescriptors-unicoderange title="section 2">2</a>
 <li>unicodeRange, <a href=#dom-fontface-unicoderange title="section 2">2</a>
 <li>[[Urls]], <a href=#dom-fontface-urls title="section 2">2</a>
+<li>variant, <a href=#dom-fontfacedescriptors-variant title="section 2">2</a>
 <li>variant, <a href=#dom-fontface-variant title="section 2">2</a>
+<li>weight, <a href=#dom-fontfacedescriptors-weight title="section 2">2</a>
 <li>weight, <a href=#dom-fontface-weight title="section 2">2</a>
 </ul></div>
 
@@ -1150,6 +1160,9 @@ <h2 class="no-num no-ref heading settled heading" id=property-index><span class=
 <a href=#issue-30993915> ↵ </a><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
+		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-28c4f329> ↵ </a></div>
+<a href=#issue-86d79dbc> ↵ </a></div>

css-font-load-events/Overview.src.html

@@ -762,7 +762,10 @@ <h3 id="document-font-face-set">
 	<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
+		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.
 
 <h2 id="font-load-event-examples">
 API Examples</h2>