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

Apply RFC 8264 enforcement only to non-empty strings #2073

Merged
merged 4 commits into from
Jul 31, 2024
Merged

Apply RFC 8264 enforcement only to non-empty strings #2073

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c0b9c94
Disallow empty strings
selfissued May 20, 2024
0bf92e2
Update index.bs
selfissued May 20, 2024
aee3cdb
Apply RFC 8264 enforcement only to non-empty strings
selfissued Jul 17, 2024
787585f
Resolved merge conflict
selfissued Jul 17, 2024
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
7 changes: 4 additions & 3 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3285,14 +3285,15 @@ credential.

- [=[RPS]=] SHOULD perform enforcement, as prescribed in Section 2.3 of
[[!RFC8266]] for the Nickname Profile of the PRECIS FreeformClass [[!RFC8264]],
when setting {{PublicKeyCredentialUserEntity/displayName}}'s value, or displaying the value to the user.
when setting {{PublicKeyCredentialUserEntity/displayName}}'s value to a non-empty string,
or displaying a non-empty value to the user.

- This string MAY contain language and direction metadata. [=[RPS]=] SHOULD consider providing this information. See [[#sctn-strings-langdir]] about how this metadata is encoded.

- [=Clients=] SHOULD perform enforcement, as prescribed in Section 2.3 of
[[!RFC8266]] for the Nickname Profile of the PRECIS FreeformClass [[!RFC8264]],
on {{PublicKeyCredentialUserEntity/displayName}}'s value prior to displaying the value to the user or
including the value as a parameter of the [=authenticatorMakeCredential=] operation.
on {{PublicKeyCredentialUserEntity/displayName}}'s value prior to displaying a non-empty value to the user or
including a non-empty value as a parameter of the [=authenticatorMakeCredential=] operation.

When [=clients=], [=client platforms=], or [=authenticators=] display a {{PublicKeyCredentialUserEntity/displayName}}'s value, they should always use UI elements to provide a clear boundary around the displayed value, and not allow overflow into other elements [[css-overflow-3]].

Expand Down