Missing data for Permissions API descriptor
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Missing compatibility data
What information was incorrect, unhelpful, or incomplete?
some features are supported in browser implement but its bcd item not added yet
- background-fetch
- nfc (android only feature)
- display-capture
- idle-detection
- periodic-background-sync
- system-wake-lock (non-standard API? implement but the referred feature not enabled)
- captured-surface-control (non-standard API? implement but the referred feature not enabled)
- speaker-selection (implement but the referred feature not enabled)
- keyboard-lock
- pointer-lock
- fullscreen (?)
- web-app-installation (implement but the referred feature not enabled)
none
- background-fetch
- bluetooth
- display-capture
- nfc
- speaker-selection
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari
What did you expect to see?
add those data
Did you test this? If so, how?
test in browser console (windows 11 or android)
test environment:
chrome M130
chrome android M124
test code:
navigator.permissions.query({
name: 'xxx'
})
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
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 reviewing the Chromium permission_descriptor.idl, Firefox Permissions.webidl, and WebKit PermissionName.idl links in the issue, then inspect the existing Permissions API data in this repository. Verify which listed permission names are implemented and supported by each browser before adding the corresponding compatibility data; done means the supported entries are represented consistently and validated by the repository checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100