- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2018 22:23:32 +0000
- To: public-webauthn@w3.org
> Arbitrary JS values are not transformed into strings OK. That includes `String` objects? And again, this needs to be clearly defined somewhere. > I think that JSON string should be DOMstring Fine, so array of 16-bit integers.... > Unpaired surrogate processing would be the same as for an other Web interface using strings. Mostly they pass them through unchanged, when using DOMString (which isn't a string of Unicode characters, name notwithstanding; it's an array of 16-bit integers). But CBOR major type 3 requires input be a Unicode string afaict, so you need to produce a Unicode string somewhere here. Again, a DOMString is not a Unicode string. You could do a USVString instead of DOMString. That would at least give you a Unicode string and clearly define how you produce it from whatever you're handed. Unpaired surrogates would be replaced with U+FFFD per <https://heycam.github.io/webidl/#dfn-obtain-unicode>. Again, I'm just repeating things I already said in https://github.com/w3c/webauthn/issues/626#issuecomment-337118928 -- GitHub Notification of comment by bzbarsky Please view or discuss this issue at https://github.com/w3c/webauthn/issues/626#issuecomment-356434016 using your GitHub account
Received on Tuesday, 9 January 2018 22:23:34 UTC