Skip to content

Commit fc66fa1

Browse files
ADKastersvgeesus
authored andcommitted
[css-font-loading-3][editorial] Reference WebIDL BufferSource
Rather than defining a custom BinaryData typedef, the FontSource interface should just use the BufferSource definition from WebIDL. https://webidl.spec.whatwg.org/#BufferSource
1 parent 667d3d3 commit fc66fa1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

css-font-loading-3/Overview.bs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The <code>FontFace</code> Interface</h2>
7777

7878
The {{FontFace}} interface represents a single usable font face.
7979
CSS ''@font-face'' rules implicitly define FontFace objects,
80-
or they can be constructed manually from a url or binary data.
80+
or they can be constructed manually from a url or a buffer source.
8181

8282
<xmp class="idl">
8383
dictionary FontFaceDescriptors {
@@ -208,7 +208,7 @@ The Constructor</h3>
208208

209209
A {{FontFace}} can be constructed either
210210
from a URL pointing to a font face file,
211-
or from an {{ArrayBuffer}} (or {{ArrayBufferView}}) containing the binary representation of a font face.
211+
or from a {{BufferSource}} containing the binary representation of a font face.
212212

213213
When the <dfn constructor for=FontFace>FontFace(family, source, descriptors)</dfn> method is called,
214214
execute these steps:
@@ -315,7 +315,7 @@ The <code>load()</code> method</h3>
315315

316316
The {{FontFace/load()}} method of {{FontFace}}
317317
forces a url-based font face to request its font data and load.
318-
For fonts constructed from binary data,
318+
For fonts constructed from a buffer source,
319319
or fonts that are already loading or loaded,
320320
it does nothing.
321321

0 commit comments

Comments
 (0)