Skip to content

Conversation

TimvdLippe
Copy link
Contributor

@TimvdLippe TimvdLippe commented Oct 6, 2025

The destination field in link options is initialized to the empty string
and can no longer be nullable. Therefore the null check is no longer
valid, since the destination is always set to a non-null value. Secondly,
we already initialize to the empty string and therefore don't need
to reassign the value to the empty string during prefetch loading.

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
    • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
    • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
  • Corresponding HTML AAM & ARIA in HTML issues & PRs:
  • MDN issue is filed: …
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


/links.html ( diff )
/semantics.html ( diff )

The destination field in link options is initialized to the empty string
and can no longer be nullable. Therefore the null check is no longer
valid, since the destination is always set to a non-null value. Secondly,
we already initialize to the empty string and therefore don't need
to reassign the value to the empty string during prefetch loading.
Copy link
Collaborator

@noamr noamr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for working on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants