[css-font-loading] Async algos are hard, yo.

Author: tabatkins

css-font-loading/Overview.bs

@@ -657,16 +657,14 @@ Events</h3>
 
 	5. Queue a task to perform the following steps synchronously:
 
-		1. <a>Fire a font load event</a> named {{loadingdone}} at <var>font face set</var>
-			with the (possibly empty) contents of <var>font face set's</var> {{[[LoadedFonts]]}} slot.
-		2. Reset the {{[[LoadedFonts]]}} slot to an empty list.
-
-	6. Queue a task to perform the following steps synchronously:
-
-		1. If <var>font face set's</var> {{[[FailedFonts]]}} slots is non-empty,
+		1. Let <var>loaded fonts</var> be the (possibly empty) contents of <var>font face set's</var> {{[[LoadedFonts]]}} slot.
+		2. Let <var>failed fonts</var> be the (possibly empty) contents of <var>font face set's</var> {{[[FailedFonts]]}} slot.
+		3. Reset the {{[[LoadedFonts]]}} and {{[[FailedFonts]]}} slots to empty lists.
+		4. <a>Fire a font load event</a> named {{loadingdone}} at <var>font face set</var>
+			with <var>loaded fonts</var>.
+		5. If <var>font face set's</var> <var>failed fonts</var> is non-empty,
 			<a>fire a font load event</a> named {{loadingerror}} at <var>font face set</var>
-			with the contents of <var>font face set's</var> {{[[FailedFonts]]}} slot.
-		2. Reset the {{[[FailedFonts]]}} slot to an empty list.
+			with <var>failed fonts</var>.
 
 	Whenever a {{FontFaceSet}} goes from <a>pending on the environment</a> to not <a>pending on the environment</a>,
 	the user agent must run the following steps: