Skip to content

Update the design-principles#consent reference to #user-intent. #196

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

Merged
jyasskin merged 1 commit into from
Nov 20, 2025
+3 −3
Merged

Update the design-principles#consent reference to #user-intent. #196

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ which can then be safely exposed to the origin. [[WEBAUTHN]]

Personal information, PII, or their derivatives
should not be exposed to origins
without [meaningful user consent](https://w3ctag.github.io/design-principles/#consent).
without [[DESIGN-PRINCIPLES#user-intent|meaningful user consent]].
Many APIs
use the Permissions API to acquire meaningful user consent.
[[PERMISSIONS]]
Expand Down Expand Up @@ -234,7 +234,7 @@ without a separate permissions prompt.
See also

* [[#user-mediation]]
* [[DESIGN-PRINCIPLES#consent]]
* [[DESIGN-PRINCIPLES#user-intent]]

<h3 class=question id="sensitive-data">
How do the features in your specification deal with sensitive information?
Expand Down Expand Up @@ -467,7 +467,7 @@ If features in your spec expose such data
and does not define adequate mitigations,
you should ensure that such information
is not revealed to origins
without [[DESIGN-PRINCIPLES#consent|meaningful user consent]],
without [[DESIGN-PRINCIPLES#user-intent|meaningful user consent]],
and
you should clearly describe this
in your specification's Security and Privacy Considerations sections.
Expand Down