refactor ServiceWorker spec to use the Storage spec
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
In order to support partitioning service workers we will need to update the spec to be written in terms of the storage spec. In particular, the service worker spec needs to use storage keys instead of origins.
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 Service Worker specification and the linked Storage specification sections on storage keys. Find the Service Worker algorithms and definitions that currently use origins, then update the relevant references so partitioned service workers are described in terms of storage keys; done means the spec consistently follows the Storage spec without origin-based gaps.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100