- From: philomathic_life via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Nov 2024 15:08:43 +0000
- To: public-webauthn@w3.org
zacknewman has just created a new issue for https://github.com/w3c/webauthn: == Replace `USVString` with `DOMString` == It would appear that the same justification that was used for #2115 applies to the remaining areas where `USVString` is used : > As recommended by the [Web IDL spec](https://webidl.spec.whatwg.org/#idl-USVString): > >> Specifications should only use `USVString` for APIs that perform text processing and need a string of scalar values to operate on. Most APIs that use strings should instead be using `DOMString`, which does not make any interpretations of the code units in the string. When in doubt, use `DOMString`. Currently the only places where `USVString` is used are the following extensions: * [`appid`](https://w3c.github.io/webauthn/#dom-authenticationextensionsclientinputs-appid) * [`appidExclude`](https://w3c.github.io/webauthn/#dom-authenticationextensionsclientinputs-appidexclude) * [`prf`](https://w3c.github.io/webauthn/#dictdef-authenticationextensionsprfinputs) Should these all be changed to `DOMString`? Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2203 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 November 2024 15:08:44 UTC