Suitability for inclusion
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Having a new HTML element to grant permissions for APIs that are restricted to JavaScript feels a little superfluous.
If this is a path forward for adding such elements in the future, for example where a <video tag can access a webcam directly, or an <location tag can show current location, maybe it would make more sense, but I think that it should be part of that proposal.
Even then, it can be argued that it could be reduced to an attribute for those elements, or left out completely to have users grant permissions on first use as is the status quo in most browsers.
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 by reading the PEPC explainer and comparing the proposed permission element with the HTML, video, and location examples raised here. Done means recording a project decision about whether this proposal belongs in PEPC and, if it does, defining its broader scope; the issue names no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100