You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LibWeb: Convert Ladybird notes in spec steps to // NB: ...
We have a couple of ways to designate spec notes and (our) developer
notes in comments, but we never really settled on a single approach. As
a result, we have a bit of a mixed bag of note comments on our hands.
To the extent that I could find them, I changed developer notes to
`// NB: ...` and changed spec notes to `// NOTE: ...`. The rationale for
this is that in most web specs, notes are prefixed by `NOTE: ...` so
this makes it easier to copy paste verbatim. The choice for `NB: ...` is
pretty arbitrary, but it makes it stand out from the regular spec notes
and it was already in wide use in our codebase.
// Spec-Note: Event handler for the load or error events could have started another load, if that happens the loadend event for this load is not fired.
261
+
// NOTE: Event handler for the load or error events could have started another load, if that happens
262
+
// the loadend event for this load is not fired.
262
263
}));
263
264
264
265
return;
@@ -278,7 +279,8 @@ WebIDL::ExceptionOr<void> FileReader::read_operation(Blob& blob, Type type, Opti
// 5. Let continue be the result of firing an event named command at target, using CommandEvent, with its command attribute initialized to command, its source attribute initialized to element, and its cancelable and composed attributes initialized to true.
227
-
// SPEC-NOTE: DOM standard issue #1328 tracks how to better standardize associated event data in a way which makes sense on Events. Currently an event attribute initialized to a value cannot also have a getter, and so an internal slot (or map of additional fields) is required to properly specify this.
226
+
// 5. Let continue be the result of firing an event named command at target, using CommandEvent, with its
227
+
// command attribute initialized to command, its source attribute initialized to element, and its cancelable
228
+
// and composed attributes initialized to true.
229
+
// NOTE: DOM standard issue #1328 tracks how to better standardize associated event data in a way which makes
230
+
// sense on Events. Currently an event attribute initialized to a value cannot also have a getter, and so
231
+
// an internal slot (or map of additional fields) is required to properly specify this.
result = TRY(resolve_imports_match(normalized_specifier.to_byte_string(), as_url, import_map.imports()));
158
158
159
159
// 12. If result is null, set it to asURL.
160
-
// Spec-Note: By this point, if result was null, specifier wasn't remapped to anything by importMap, but it might have been able to be turned into a URL.
160
+
// NOTE: By this point, if result was null, specifier wasn't remapped to anything by importMap, but it might have
0 commit comments