mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-12-08 06:09:58 +00:00
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.
This commit is contained in:
parent
9394c9a10b
commit
41eb7251e4
Notes:
github-actions[bot]
2025-11-18 14:09:02 +00:00
Author: https://github.com/gmta
Commit: 41eb7251e4
Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/6841
Reviewed-by: https://github.com/trflynn89
11 changed files with 52 additions and 44 deletions
|
|
@ -157,7 +157,8 @@ WebIDL::ExceptionOr<URL::URL> resolve_module_specifier(Optional<Script&> referri
|
|||
result = TRY(resolve_imports_match(normalized_specifier.to_byte_string(), as_url, import_map.imports()));
|
||||
|
||||
// 12. If result is null, set it to asURL.
|
||||
// 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.
|
||||
// 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.
|
||||
if (!result.has_value())
|
||||
result = as_url;
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue