- From: asmusf via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Jul 2018 01:25:07 +0000
- To: public-webauthn@w3.org
Strongly second @aphillips here. For what you want, characters are the natural unit, and determining **_character_** boundaries is not going to challenge embedded processors. Determining character boundaries is also something that's absolutely stable, unlike extended grapheme clusters. Their design premise is strongly biased towards user interfaces, so, for example, if you were to present a truncated name, you might want to add ellipses at the last EGC boundary inside the 64 character (or longer) window to which the name has been truncated to. But that would be done on the client level. I am wondering about the fact that the usage seems to be in the context of authentication. Is the username (truncated) used for authentication purposes ? If so, does it make a difference if different authenticators implement different limits? -- GitHub Notification of comment by asmusf Please view or discuss this issue at https://github.com/w3c/webauthn/issues/973#issuecomment-403179301 using your GitHub account
Received on Saturday, 7 July 2018 01:25:10 UTC