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

make "capability doesn't exist" and "permission denied" look the same #147

Open
samuelweiler opened this issue Sep 21, 2022 · 0 comments
Open

make "capability doesn't exist" and "permission denied" look the same #147

samuelweiler opened this issue Sep 21, 2022 · 0 comments
Assignees
@hober
Labels
enhancement proposed normative change new question proposal to add a new question

Comments

@samuelweiler
Copy link
Contributor

We should document, as an extension of https://w3ctag.github.io/design-principles/#do-not-expose-use-of-private-browsing-mode, that behavior when permission for a feature (or sensor) is denied should be indistinguishable from when it doesn't exist.

This came up in the Devices and Sensors WG meeting at TPAC2022.
@hober hober self-assigned this Aug 1, 2023
@hober hober added the enhancement proposed normative change label Aug 1, 2023
@hober hober added the new question proposal to add a new question label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hober hober

Labels
enhancement proposed normative change new question proposal to add a new question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hober @samuelweiler and others