Re: [webauthn] Certain issues in client extension pass-through specification (#1273)

As you have stated, the javascript type will almost always be `Number`.

My interpretation of this statement has been, if the client does not understand an extension (such as `authenticatorBiometricPerfBounds`, it must detect whether a value is an integer. If so, it sends it as a CBOR integer. If not, it sends it as a 64-bit floating point value.

So in this example, `FAR` and `FRR` represent values from zero to one, inclusive. If the client did not understand this extension and the javascript request had either a value of 0.0 or 1.0 for either of these parameters, that parameter would be sent to the authenticator not as a 64 bit floating point value - but as a positive integer.

-- 
GitHub Notification of comment by dwaite
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1273#issuecomment-520123255 using your GitHub account

Received on Saturday, 10 August 2019 06:37:48 UTC