SecurityError vs NotAllowedError for "allowed to use" check
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
If this's relevant global object's associated Document is not allowed to use the "payment" permission, then throw a "SecurityError" DOMException.
Should this not throw an "NotAllowedError" exception instead?
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 comparing the linked Payment Request specification text with the WebIDL definitions for SecurityError and NotAllowedError, and review the allowed-to-use permission requirement. Determine which exception matches this check and update the specification wording once the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100