[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Define the default allowlist normatively #382

Open
anssiko opened this issue Feb 8, 2019 · 3 comments
Open

Define the default allowlist normatively #382

anssiko opened this issue Feb 8, 2019 · 3 comments

Comments

@anssiko
Copy link
Member
anssiko commented Feb 8, 2019

The constructors of concrete sensor specs invoke "Construct a FooSensor object" abstract operation (e.g. accelerometer and gyroscope) that in turn invokes Check sensor policy-controlled features defined in the Generic Sensor API.

These abstract operations take care of Feature Policy integration as specified in the Extending the Feature Policy API section of the Generic Sensor API except that the default allowlist is not normatively defined. It is defined in the above-mentioned non-normative section of the Generic Sensor API as follow:

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

A proposed fix would be to make this text normative by moving it into the normative Sensor section.
@anssiko
Copy link
Member Author
anssiko commented Feb 8, 2019

Just appeared to me the above proposal assumes policy-controlled features that extend Sensor would inherit its default allowlist.

@clelland given an example interface Accelerometer : Sensor { }; how to correctly define that Accelerometer inherits the default allowlist of Sensor?

@rakuco
Copy link
Member
rakuco commented Aug 27, 2021

I think this is also related to the discussions in the DAS WG 2021 Q2 virtual meeting, where there was a resolution saying we would "Make default allowlist "self" for the Generic Sensor API, include non-normative language in concrete sensor specs to make it clear those features are Permissions Policy controlled features".

@anssiko
Copy link
Member Author
anssiko commented Aug 27, 2021

I just submitted w3c/accelerometer#61

It deviates slightly from the TPAC resolution, PTAL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rakuco @anssiko