Order of messages to clients in same unit of related browsing contexts unclear
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
The spec doesn't seem to require that messages sent from a service worker to two clients which belong to the same unit of related browsing contexts arrive in the same order they were sent. Without this property it's not possible to observe the state where a client is loading and hasn't called ServiceWorkerContainer.startMessages() yet, but has a queued message. This, in turn, makes it impossible to test it with some implementation-specific interface, potentially harming compatibility.
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 with the ServiceWorkerContainer.startMessages() entry point and the specification text governing messages sent from a service worker to clients in the same unit of related browsing contexts. Determine whether message ordering and queued-message visibility are normatively defined, and document a precise requirement that makes the described state observable and testable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100