Can we expose Crypto/SubtleCrypto to all Worklet / all scopes?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Is there any concern exposing Crypto/SubtleCrypto to all scopes, or all Worklet scopes, rather than just (Window, Worker)?
This is a desirable feature for the shared storage worklet (e.g. will make the aggregation key generation process easier).
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
The issue names Crypto/SubtleCrypto and Worklet scopes but does not identify files, tests, or an implementation entry point. Start by locating the specification sections that define the exposed scopes and review the shared storage worklet use case. Done means reaching a decided, documented scope for exposure, with corresponding specification and test changes identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100