Skip to content

Editorial: Remove an invalid structured serialization assertion - #13131

Open
JinDX wants to merge 1 commit into
whatwg:mainfrom
JinDX:editorial/structured-clone-transfer-assertion
Open

JinDX wants to merge 1 commit into
whatwg:mainfrom
JinDX:editorial/structured-clone-transfer-assertion

Conversation

@JinDX

@JinDX JinDX commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

Remove the assertion that a serialized viewed buffer already has a completed buffer type. StructuredSerializeWithTransfer prepopulates memory with transfer placeholders whose Type is not initialized until after the initial serialization.

For example, serializing a Uint8Array while transferring its underlying ArrayBuffer can return such a placeholder here. The remaining algorithm already retains that record for later completion.

Spec: https://html.spec.whatwg.org/multipage/structured-data.html#structuredserializeinternal

  • 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.)


/structured-data.html ( diff )

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.

1 participant