- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 May 2019 22:19:57 +0000
- To: public-webauthn@w3.org
> What I'd want to avoid is people writing lots of machinery to check for this state, when in practice their transcoder and the [[Encoding]] spec have already handled this. Ok, thanks for the info. I have dropped this wording. > The client […] won't be able to necessarily detect a truncated grapheme. That is correct. Hopefully truncation does not happen often and authenticators are more generous with space than strictly required. > I believe the RP information is only ever displayed by the authenticator itself, so if it wishes to alter the data (such as truncating it) then it is responsible for doing so appropriately. Authenticators do not have to have displays. If they do not then an account selection dialog is shown by the user-agent if there is more than one credential to choose between. That dialog will contain the RP information as provided (and truncated) by the authenticator. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1205#issuecomment-491446220 using your GitHub account
Received on Friday, 10 May 2019 22:19:58 UTC