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.

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

Explicitly specify binary encoding for string truncation #2017

Merged
merged 8 commits into from
May 27, 2024

Conversation

emlun
Copy link
Member

@emlun emlun commented Jan 19, 2024

Fixes #1994.


Preview | Diff

@emlun emlun requested review from agl and aphillips January 19, 2024 14:33
Copy link

@aphillips aphillips left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for copying me on this PR. Some suggestions...

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@emlun emlun force-pushed the issue-1994-binary-trunc-encoding branch from a7c2ded to 527629c Compare January 22, 2024 16:24
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@nadalin nadalin added this to the L3-WD-02 milestone Feb 21, 2024
@emlun emlun force-pushed the issue-1994-binary-trunc-encoding branch from 9b7e211 to 8f89a8e Compare February 28, 2024 12:28
index.bs Outdated Show resolved Hide resolved
@plehegar plehegar added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Mar 13, 2024
index.bs Outdated Show resolved Hide resolved
@emlun emlun requested review from agl and aphillips March 20, 2024 15:23
@agl
Copy link
Contributor

agl commented May 15, 2024

From the call of 2024-05-15: ok to land after agl reviews.

@@ -3194,7 +3194,9 @@ associated with or [=scoped=] to, respectively.

When [=clients=], [=client platforms=], or [=authenticators=] display a {{PublicKeyCredentialEntity/name}}'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]].

Authenticators MAY truncate a {{PublicKeyCredentialEntity/name}} member's value so that it fits within 64 bytes, if the authenticator stores the value. See [[#sctn-strings-truncation]] about truncation and other considerations.
When storing a {{PublicKeyCredentialEntity/name}} member's value,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor nit: this comma (and in the next diff hunk) read oddly to me, but I'm happy either way.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I see. If you don't mind I'll keep it as is, if only for consistency with the first sentence in the paragraph immediately preceding this (and also the next hunk).

@emlun emlun merged commit fabbc09 into main May 27, 2024
2 checks passed
@emlun emlun deleted the issue-1994-binary-trunc-encoding branch May 27, 2024 13:28
github-actions bot added a commit that referenced this pull request May 27, 2024
SHA: fabbc09
Reason: push, by emlun

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. type:technical
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rp.name, user.name and user.displayName length limit does not state binary encoding
5 participants