Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not.
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Compare https://html.spec.whatwg.org/#dom-messageport-postmessage and https://w3c.github.io/ServiceWorker/#dom-serviceworker-postmessage . source is special in service workers, fine, but I'm confused as to why the inconsistency in origin.
I think the best fix might be to set origin for Workers too, but I am not sure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the HTML MessagePort postMessage definition with the Service Worker postMessage definition in the linked specifications. Determine whether Worker MessageEvents should set origin and document the intended behavior in the relevant specification text. Done means the inconsistency has a clear resolution in the spec.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100