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

Add a Permissions Policy Integration section #60

Closed

Conversation

sideshowbarker
Copy link

@sideshowbarker sideshowbarker commented Mar 24, 2021

@anssiko
Copy link
Member

anssiko commented Mar 25, 2021

@sideshowbarker, thanks!

The current integration is through https://w3c.github.io/sensors/#check-sensor-policy-controlled-features that is called into from https://w3c.github.io/accelerometer/#construct-an-accelerometer-object (and other sensor APIs that inherit from Sensor).

The feature strings are defined in https://w3c.github.io/permissions/#permission-registry

It seems if we'd make the following default allowlist normative in the Generic Sensor API (from https://w3c.github.io/sensors/#permissions-policy-api):

The features' default allowlist is ["self"].

... that'd satisfy this requirement without needing to add a Permissions Policy Integration section into each concrete sensor API spec?

@reillyeon @clelland for review of the idea.

@sideshowbarker
Copy link
Author

The current integration is through w3c.github.io/sensors/#check-sensor-policy-controlled-features that is called into from w3c.github.io/accelerometer/#construct-an-accelerometer-object (and other sensor APIs that inherit from Sensor).

The feature strings are defined in w3c.github.io/permissions/#permission-registry

aha — thanks

It seems if we'd make the following default allowlist normative in the Generic Sensor API (from w3c.github.io/sensors/#permissions-policy-api):

The features' default allowlist is ["self"].

... that'd satisfy this requirement without needing to add a Permissions Policy Integration section into each concrete sensor API spec?

Sounds right to me

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

Successfully merging this pull request may close these issues.

2 participants