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.

Sign up for GitHub

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

Jump to bottom

Editorial: cleanup postMessage() invocation for dedicated workers #4140

Open
annevk opened this issue Oct 29, 2018 · 1 comment
Open

Editorial: cleanup postMessage() invocation for dedicated workers #4140

annevk opened this issue Oct 29, 2018 · 1 comment
Labels
good first issue Ideal for someone new to a WHATWG standard or software project

Comments

@annevk
Copy link
Member

annevk commented Oct 29, 2018

Instead of language such as

The postMessage(message, transfer) and postMessage(message, options) methods on Worker objects act as if, when invoked, they immediately invoked the respective postMessage(message, transfer) and postMessage(message, options) on the port, with the same arguments, and returned the same return value.

which we use for both Worker and DedicatedWorkerGlobalScope we should use a shared abstract operation so that we don't invoke a public API.
@annevk annevk added the good first issue Ideal for someone new to a WHATWG standard or software project label Oct 29, 2018
@acharyasourav
Copy link

Hey, @annevk I would like to work on this can you please elaborate on what needs to be done? Also, where should I start looking?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Ideal for someone new to a WHATWG standard or software project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@annevk @acharyasourav