Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the API re PostMessageOptions vs StructuredSerializeOptions #15

Merged
merged 1 commit into from
Dec 15, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,9 +138,11 @@ dictionary WindowPostMessageOptions : PostMessageOptions {
USVString targetOrigin = "/";
};

dictionary PostMessageOptions {
sequence<object> transfer = [];
boolean includeUserActivation = false;
// Note that this reintroduces a dictionary named `PostMessageOptions`, which
// was renamed to `StructuredSerializeOptions` in
// https://github.com/whatwg/html/pull/3414
dictionary PostMessageOptions : StructuredSerializeOptions {
boolean includeUserActivation = false;
};

partial interface Window {
Expand All @@ -155,4 +157,7 @@ partial interface MessagePort {
void postMessage(any message, PostMessageOptions options);
};

// Note that structuredClone in the WindowOrWorkerGlobalScope interface still
// takes StructuredSerializeOptions, not PostMessageOptions

```