Skip to content

Commit 6450078

Browse files
csarvenjyasskinmarcoscaceres
authored
Add loyalty guidance for facilitating users switching UAs (#28)
* Add loyalty guidance for users switching UAs Closes #5 * Apply suggestion from @jyasskin Co-authored-by: Jeffrey Yasskin <[email protected]> * Clarify credentials and OS-stored passkeys re switching UA * Change passkey to credentials example for OS storage Co-authored-by: Marcos Cáceres <[email protected]> * Clarify relying on OS stored credentials and reuse Co-authored-by: Jeffrey Yasskin <[email protected]> * Editorial on relying on and access for OS stored credentials --------- Co-authored-by: Jeffrey Yasskin <[email protected]> Co-authored-by: Marcos Cáceres <[email protected]>
1 parent 4f23c13 commit 6450078

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

index.bs

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,11 @@ A user agent can also help its user
153153
make a credible commitment to a page in order to get that page's services,
154154
and it's not disloyal to maintain that commitment after getting the services.
155155

156+
A user agent must not obstruct its users from switching to another user agent.
157+
For example, it must not block access to, export, or store user data in ways that prevent portability.
158+
This includes identity information, bookmarks, history, passwords, and credentials such as passkeys.
159+
If the user agent relies on the underlying <abbr title="Operating System">OS</abbr> to store credentials,
160+
there needs to be a way for users to allow other user agents to access those credentials.
156161

157162
<section class="non-normative">
158163

0 commit comments

Comments
 (0)