Permissions Policy integration
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
CPU Performance API by design provides a non-trivial risk of fingerprinting. Is there a plan to add a Permissions/Feature Policy integration?
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
No files, tests, or implementation entry points are identified in the issue. Start by reviewing the CPU Performance API proposal and the relevant Permissions/Feature Policy requirements, then clarify the integration scope and acceptance criteria with maintainers; done would be an agreed plan or a concrete follow-up issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100