- From: philomathic_life via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Aug 2024 17:26:35 +0000
- To: public-webauthn@w3.org
> User agents are expected to _not_ re-encode `id`, so yes, `id` and `rawId` are essentially aliases in the `*ResponseJSON` context. Fair point about the `Base64URLString` type perhaps making it seem like it would be doubly-encoded, but on the other hand it _is_ a base64 encoded value. @MasterKale any thoughts on that? I don't find that argument convincing considering there are other fields that _are_ something more specific but nonetheless retain the same more general type. In particular `clientDataJSON` _is_ a `USVString` which _is_ a `DOMString`; yet it's still modeled as an `ArrayBuffer` and `USVString`s are often modeled as `DOMString`s. -- GitHub Notification of comment by zacknewman Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2119#issuecomment-2284554967 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 August 2024 17:26:36 UTC