Behavior for accessing cache storage in opaque origins
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 currently describe if there should be any special behavior when trying to use the cache storage API in an opaque origin. From some research somebody did, it appears both Chrome and Firefox currently throw when accessing self.caches from an opaque origin. If that is indeed the desired behavior https://w3c.github.io/ServiceWorker/#global-caches should probably be updated to actually document that behavior?
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 Cache Storage API section at https://w3c.github.io/ServiceWorker/#global-caches and review the linked native-file-system research about opaque origins. Determine whether throwing when accessing self.caches is the intended interoperable behavior, then update the specification to document the resolved behavior. Done means the opaque-origin case is explicitly covered in the spec.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100