Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need a "permission" type? #8

Open
marcoscaceres opened this issue Jun 22, 2021 · 2 comments
Open

Do we need a "permission" type? #8

marcoscaceres opened this issue Jun 22, 2021 · 2 comments

Comments

@marcoscaceres
Copy link
Contributor

marcoscaceres commented Jun 22, 2021

It's increasingly common for specs define a permission string (list below) for the purpose of integrating with the Permissions Policy spec. See example from Payment Request.

Should we add a special type for those? Similar to the "event" type.

  • accelerometer
  • ambient-light-sensor
  • background-fetch
  • background-sync
  • bluetooth
  • camera
  • clipboard-write
  • device-info
  • display-capture
  • gamepad
  • geolocation
  • gyroscope
  • magnetometer
  • microphone
  • midi
  • nfc
  • notifications
  • payment
  • persistent-storage
  • push
  • speaker-selection
@marcoscaceres marcoscaceres changed the title Do we need a permissions type? Do we need a "permission" type? Jun 22, 2021
@marcoscaceres
Copy link
Contributor Author

ReSpec supports labelling things as permissions.

@dontcallmedom
Copy link
Member

this landed in reffy, webref, bikeshed too; missing support in xref atm

dontcallmedom added a commit to speced/respec-web-services that referenced this issue Feb 28, 2022
marcoscaceres pushed a commit to speced/respec-web-services that referenced this issue Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants