Enabling client message queue on DOMContentLoaded is not mentioned in the spec
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
In issue #728 changes were made both to this and the HTML spec, adding the ServiceWorkerContainer.startMessages() method and revising the way messages sent via Client.postMessage() are dispatched. Unfortunately, it's not clear from this spec alone that the client message queue is enabled when the DOMContentLoaded event is fired, as this detail is part of the HTML spec. I think an informative note would be very helpful here.
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 reading the changes from issue #728 and the sections covering ServiceWorkerContainer.startMessages() and Client.postMessage() dispatch. Confirm how the HTML spec ties client message-queue enabling to DOMContentLoaded, then add an informative note to this Service Worker specification explaining that relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100