8000 [css-font-loading] Turn local font issue into a note about planned fu… · w3c/csswg-drafts@62acd3b · GitHub
Skip to content

Commit 62acd3b

Browse files
tabatkinstabatkins
committed
[css-font-loading] Turn local font issue into a note about planned future behavior.
1 parent bfc1c81 commit 62acd3b

2 files changed

Lines changed: 5 additions & 25 deletions

File tree

‎css-font-loading/Overview.bs‎

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -760,13 +760,8 @@ Interaction with CSS’s ''@font-face'' Rule</h3>
760760
All non-<a>CSS-connected</a> <a interface>FontFace</a> objects must be sorted after the <a>CSS-connected</a> ones,
761761
in insertion order.
762762

763-
<p class='issue'>
764-
Can/should we include the local system fonts,
765-
or is that a fingerprinting problem?
766-
I think the set of local fonts is trivially discoverable anyway.
767-
Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
768-
and perhaps can be queried against?
769-
This would make FontFaceSet fully explain the current behavior of fonts.
763+
Note: It is expected that a future version of this specification
764+
will define ways of interacting with and querying local fonts as well.
770765

771766
<h2 id="font-load-event-examples">
772767
API Examples</h2>

‎css-font-loading/Overview.html‎

Lines changed: 3 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -106,8 +106,7 @@ <h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class
106106
< 10BC0 span class=pl-kos><li><a href=#normative><span class=secno></span> Normative References</a>
107107
<li><a href=#informative><span class=secno></span> Informative References</a></ul>
108108
<li><a href=#index><span class=secno></span> Index</a>
109-
<li><a href=#property-index><span class=secno></span> Property index</a>
110-
<li><a href=#issues-index><span class=secno></span>Issues Index</a></ul></div>
109+
<li><a href=#property-index><span class=secno></span> Property index</a></ul></div>
111110

112111

113112

@@ -844,13 +843,8 @@ <h3 class="heading settled heading" data-level=4.2 id=document-font-face-set><sp
844843
<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,
845844
in insertion order.
846845

847-
<p class=issue id=issue-d3a24efa><a class=self-link href=#issue-d3a24efa></a>
848-
Can/should we include the local system fonts,
849-
or is that a fingerprinting problem?
850-
I think the set of local fonts is trivially discoverable anyway.
851-
Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
852-
and perhaps can be queried against?
853-
This would make FontFaceSet fully explain the current behavior of fonts.
846+
<p class=note> Note: It is expected that a future version of this specification
847+
will define ways of interacting with and querying local fonts as well.
854848

855849
<h2 class="heading settled heading" data-level=5 id=font-load-event-examples><span class=secno>5 </span><span class=content>
856850
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=
11611155
<div data-fill-with=property-index><p>No properties defined.</div>
11621156

11631157

1164-
<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>
1165-
Can/should we include the local system fonts,
1166-
or is that a fingerprinting problem?
1167-
I think the set of local fonts is trivially discoverable anyway.
1168-
Alternately, define a specialized variant of FontFace which represents all the local fonts collectively,
1169-
and perhaps can be queried against?
1170-
This would make FontFaceSet fully explain the current behavior of fonts.
1171-
1172-
<a href=#issue-d3a24efa> ↵ </a></div></div>

0 commit comments

Comments
 (0)