- From: philomathic_life via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 May 2024 21:14:01 +0000
- To: public-webauthn@w3.org
zacknewman has just created a new issue for https://github.com/w3c/webauthn: == Make AuthenticatorAttestationResponseJSON.publicKeyAlgorithm a long == [`COSEAlgorithmIdentifier`](https://www.w3.org/TR/webauthn-3/#typedefdef-cosealgorithmidentifier) is defined as a [`long`](https://webidl.spec.whatwg.org/#idl-long), but [`AuthenticatorAttestationResponseJSON.publicKeyAlgorithm`](https://www.w3.org/TR/webauthn-3/#dom-authenticatorattestationresponsejson-publickeyalgorithm) is a [`long long`](https://webidl.spec.whatwg.org/#idl-long-long). While RPs are likely based on 64-bit platforms, it seems unnecessary to require 64-bit signed integers when a 32-bit signed integer is sufficient. What is the reason for this deviation? Is it based on "common" JSON libraries that model numbers as 64-bit signed integers? Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2065 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 May 2024 21:14:02 UTC