Define and export "accelerometer" permission #67
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anssiko
approved these changes
Oct 18, 2022
|
Thanks @miketaylr! |
reillyeon
approved these changes
Oct 18, 2022
github-actions bot
added a commit
that referenced
this pull request
Oct 18, 2022
SHA: 34cfefb Reason: push, by reillyeon Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
rakuco
added a commit
to rakuco/magnetometer
that referenced
this pull request
Oct 24, 2023
This is similar to w3c/accelerometer#67: with this we can eventually link to the permission name from https://w3c.github.io/permissions-registry/
rakuco
added a commit
to rakuco/gyroscope
that referenced
this pull request
Oct 24, 2023
…re name * Move the permissions-policy text to a separate section for clarity. * Stop saying "Gyroscope a policy-controlled feature" because it does not make much sense. The most common way to list features is by saying something like "this spec defines a feature identifed by the string 'foo'". In our case, that string is "gyroscope". * Define and export the feature identifier above, as it is used in e.g. the Orientation Sensor specification. * Explicitly list all data associated with the spec's sensor type using a definition list instead of a very long paragraph. * Similarly to w3c/accelerometer#67, define and export the "gyroscope" permission so that we can eventually link to the permission name from https://w3c.github.io/permissions-registry/
rakuco
added a commit
to rakuco/proximity
that referenced
this pull request
Oct 26, 2023
…re name * Move the permissions-policy text to a separate section for clarity. * Stop saying "Proximity Sensor a policy-controlled feature" because it does not make much sense. The most common way to list features is by saying something like "this spec defines a feature identifed by the string 'foo'". In our case, that string is "proximity-sensor". * Define and export the feature identifier above. * Explicitly list all data associated with the spec's sensor type using a definition list instead of a very long paragraph. * Similarly to w3c/accelerometer#67, define and export the "gyroscope" permission so that we can eventually link to the permission name from https://w3c.github.io/permissions-registry/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This way we can eventually link to it from https://w3c.github.io/permissions-registry/
Preview | Diff