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
|
|
@ -244,10 +244,10 @@ WebIDL::ExceptionOr<NavigationResult> Navigation::navigate(String url, Navigatio
|
|||
// 4. Let state be options["state"], if it exists; otherwise, undefined.
|
||||
auto state = options.state.value_or(JS::js_undefined());
|
||||
|
||||
// 5. Let serializedState be StructuredSerializeForStorage(state).
|
||||
// If this throws an exception, then return an early error result for that exception.
|
||||
// Spec-Note: It is important to perform this step early, since serialization can invoke web developer code,
|
||||
// which in turn might change various things we check in later steps.
|
||||
// 5. Let serializedState be StructuredSerializeForStorage(state). If this throws an exception, then return an early
|
||||
// error result for that exception.
|
||||
// NOTE: It is important to perform this step early, since serialization can invoke web developer code, which in
|
||||
// turn might change various things we check in later steps.
|
||||
auto serialized_state_or_error = structured_serialize_for_storage(vm, state);
|
||||
if (serialized_state_or_error.is_error()) {
|
||||
return early_error_result(serialized_state_or_error.release_error());
|
||||
|
|
@ -307,10 +307,10 @@ WebIDL::ExceptionOr<NavigationResult> Navigation::reload(NavigationReloadOptions
|
|||
// 2. Let serializedState be StructuredSerializeForStorage(undefined).
|
||||
auto serialized_state = MUST(structured_serialize_for_storage(vm, JS::js_undefined()));
|
||||
|
||||
// 3. If options["state"] exists, then set serializedState to StructuredSerializeForStorage(options["state"]).
|
||||
// If this throws an exception, then return an early error result for that exception.
|
||||
// Spec-Note: It is important to perform this step early, since serialization can invoke web developer
|
||||
// code, which in turn might change various things we check in later steps.
|
||||
// 3. If options["state"] exists, then set serializedState to StructuredSerializeForStorage(options["state"]). If
|
||||
// this throws an exception, then return an early error result for that exception.
|
||||
// NOTE: It is important to perform this step early, since serialization can invoke web developer code, which in
|
||||
// turn might change various things we check in later steps.
|
||||
if (options.state.has_value()) {
|
||||
auto serialized_state_or_error = structured_serialize_for_storage(vm, options.state.value());
|
||||
if (serialized_state_or_error.is_error())
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue