[css-font-loading] Clarify that a parsing error during FontFace construction sets things to the empty string.

Author: tabatkins

css-font-loading/Overview.bs

@@ -199,75 +199,67 @@ The Constructor</h3>
 	When the <dfn method title='FontFace()' for=FontFace>FontFace</dfn>(DOMString <dfn argument for="FontFace/FontFace()">family</dfn>, (DOMString or {{BinaryData}}) <dfn argument for="FontFace/FontFace()">source</dfn>, {{FontFaceDescriptors}} <dfn argument for="FontFace/FontFace()">descriptors</dfn>) method is called,
 	execute these steps:
 
-	<ol link-type=idl>
-		<li>
-			Let <var>font face</var> be a fresh {{FontFace}} object.
-			Set <var>font face's</var> {{FontFace/status}} attribute to <code>"unloaded"</code>,
-			Set its internal {{[[FontStatusPromise]]}} slot to a fresh pending {{Promise}} object.
-
-			Parse the {{family!argument}} argument,
-			and the members of the {{descriptors!argument}} argument,
-			according to the grammars of the corresponding descriptors of the CSS ''@font-face'' rule.
-			If any of them fail to parse correctly,
-			reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError",
-			and set <var>font face’s</var> {{FontFace/status}} attribute to "error".
-			Otherwise, set <var>font face's</var> corresponding attributes to the serialization of the parsed values.
-
-			Return <var>font face</var>.
-			If <var>font face’s</a> {{FontFace/status}} is "error",
-			terminate this algorithm;
-			otherwise,
-			complete the rest of these steps asynchronously.
-
-		<li>
-			If the {{source!argument}} argument was a {{DOMString}},
-			parse it according to the grammar of the 'src' descriptor of the CSS ''@font-face'' rule.
-			If it fails to parse correctly,
-			reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError" exception,
-			queue a task to set <var>font face’s</var> {{FontFace/status}} attribute to "error",
-			and abort these steps;
-			otherwise, set <var>font face's</var> internal {{[[Urls]]}} slot to the string.
-
-			Note: Note that this means that passing a naked url as the source argument,
-			like <code>"http://example.com/myFont.woff"</code>,
-			won't work - it needs to be at least wrapped in a ''url()'' function,
-			like <code>"url(http://example.com/myFont.woff)"</code>.
-			In return for this inconvenience,
-			you get to specify multiple fallbacks,
-			specify the type of font each fallback is,
-			and refer to local fonts easily.
-
-			Issue: Need to define the base url,
-			so relative urls can resolve.
-			Should it be the url of the document?
-			Is that correct for workers too,
-			or should they use their worker url?
-			Is that always defined?
-
-			If the {{source}} argument was a {{BinaryData}},
-			set <var>font face's</var> internal {{[[Data]]}} slot to the passed argument.
-
-		<li>
-			If <var>font face's</var> {{[[Data]]}} slot is not <code>null</code>,
-			queue a task to set <var>font face's</var> {{FontFace/status}} attribute to "loading".
-			Attempt to parse the data in it as a font.
-			When this is completed,
-			successfully or not,
-			queue a task to run the following steps synchronously:
-
-			<ol>
-				<li>
-					If the load was successful,
-					<var>font face</var> now represents the parsed font;
-					fulfill <var>font face's</var> {{[[FontStatusPromise]]}} with <var>font face</var>,
-					and set its {{FontFace/status}} attribute to "loaded".
-
-				<li>
-					Otherwise,
-					reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError"
-					and set <var>font face's</var> {{FontFace/status}} attribute to "error".
-			</ol>
-	</ol>
+	1. Let <var>font face</var> be a fresh {{FontFace}} object.
+		Set <var>font face's</var> {{FontFace/status}} attribute to <code>"unloaded"</code>,
+		Set its internal {{[[FontStatusPromise]]}} slot to a fresh pending {{Promise}} object.
+
+		Parse the {{family!argument}} argument,
+		and the members of the {{descriptors!argument}} argument,
+		according to the grammars of the corresponding descriptors of the CSS ''@font-face'' rule.
+		If any of them fail to parse correctly,
+		reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError",
+		set <var>font face’s</var> corresponding attributes to the empty string,
+		and set <var>font face’s</var> {{FontFace/status}} attribute to "error".
+		Otherwise, set <var>font face's</var> corresponding attributes to the serialization of the parsed values.
+
+		Return <var>font face</var>.
+		If <var>font face’s</a> {{FontFace/status}} is "error",
+		terminate this algorithm;
+		otherwise,
+		complete the rest of these steps asynchronously.
+
+	2. If the {{source!argument}} argument was a {{DOMString}},
+		parse it according to the grammar of the 'src' descriptor of the CSS ''@font-face'' rule.
+		If it fails to parse correctly,
+		reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError" exception,
+		queue a task to set <var>font face’s</var> {{FontFace/status}} attribute to "error",
+		and abort these steps;
+		otherwise, set <var>font face's</var> internal {{[[Urls]]}} slot to the string.
+
+		Note: Note that this means that passing a naked url as the source argument,
+		like <code>"http://example.com/myFont.woff"</code>,
+		won't work - it needs to be at least wrapped in a ''url()'' function,
+		like <code>"url(http://example.com/myFont.woff)"</code>.
+		In return for this inconvenience,
+		you get to specify multiple fallbacks,
+		specify the type of font each fallback is,
+		and refer to local fonts easily.
+
+		Issue: Need to define the base url,
+		so relative urls can resolve.
+		Should it be the url of the document?
+		Is that correct for workers too,
+		or should they use their worker url?
+		Is that always defined?
+
+		If the {{source}} argument was a {{BinaryData}},
+		set <var>font face's</var> internal {{[[Data]]}} slot to the passed argument.
+
+	3. If <var>font face's</var> {{[[Data]]}} slot is not <code>null</code>,
+		queue a task to set <var>font face's</var> {{FontFace/status}} attribute to "loading".
+		Attempt to parse the data in it as a font.
+		When this is completed,
+		successfully or not,
+		queue a task to run the following steps synchronously:
+
+		1. If the load was successful,
+			<var>font face</var> now represents the parsed font;
+			fulfill <var>font face's</var> {{[[FontStatusPromise]]}} with <var>font face</var>,
+			and set its {{FontFace/status}} attribute to "loaded".
+
+		2. Otherwise,
+			reject <var>font face's</var> {{[[FontStatusPromise]]}} with a DOMException named "SyntaxError"
+			and set <var>font face's</var> {{FontFace/status}} attribute to "error".
 
 	Note: Newly constructed FontFace objects are not automatically added
 	to the FontFaceSet associated with a document