Re: [webauthn] Revert location extension back to approved PR's

There were two serious problems with the previous CBOR for the extension.  First, the required and optional fields were different than those for the W3C Geolocation API Coordinates data structure.  Second, its CBOR representation was an array, whereas the Coordinates data structure is a JavaScript object - not an array.  This means that a custom transformation would be required to support the extension - meaning that it could not be used without explicit browser support for the custom transformation; it could not be used as an unknown extension as described in #738 .  Now that the CBOR and the JavaScript directly correspond, it can.  The changes applied in #789 were part of fixing issue #738 .

You may have not paid addition to it, but there *was* substantial discussion on the list of the representation of the location extension.  See the back-and-forth between @agl , @equalsJeffH , and myself about the representation in the context of #789 .

In short, requiring a custom transformation between the authenticator extension output and the client extension output is the wrong thing to do.  Having a CBOR representation that is syntactically and semantically incompatible with the Coordinates data structure is the wrong thing to do.  Because of the corrections applied, #738 is now fixed.  The proposed reversion would break #738 again.  This must not occur.  Therefore, this issue and PR #801 must be closed with no action.

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

Received on Wednesday, 14 February 2018 17:10:52 UTC