From e05eabf098ab246fabcaff9334cab57bae9694b5 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Tue, 18 Nov 2025 14:08:02 -0800 Subject: [PATCH] Update the design-principles#consent reference to #user-intent. --- index.bs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.bs b/index.bs index cd87a3d..be1ca38 100644 --- a/index.bs +++ b/index.bs @@ -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]] @@ -234,7 +234,7 @@ without a separate permissions prompt. See also * [[#user-mediation]] -* [[DESIGN-PRINCIPLES#consent]] +* [[DESIGN-PRINCIPLES#user-intent]]

How do the features in your specification deal with sensitive information? @@ -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.