w3c / w3c/ServiceWorker

Merge with storage

Open
#1,230 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
3.6k
Forks
324
Avg merge
14d 22h
Merged PRs (30d)
1

Description

https://github.com/whatwg/storage/issues/18

Service worker registrations and cache storage should be linked to a particular storage bucket.

This explains how origin storage is purged, and makes it clear that these items are protected by persistent storage.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked WHATWG Storage issue 18 and compare its storage-bucket model with the ServiceWorker specification's treatment of service worker registrations and cache storage. Done means the specification clearly links both items to a storage bucket and explains how purging and persistent-storage protection apply.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.