- From: Mike Jones via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Feb 2018 02:42:18 +0000
- To: public-webauthn@w3.org
The previous location extension definition used the Geolocation API Coordinates data type, but didn't satisfy its requirements (especially by not providing data for a required member). That would never pass muster in W3C-wide review. The new text will. If we want to add a note to implementers about interpretations of and use of the "accuracy" field post-CR, we can do that. I didn't file a separate PR because this was only one of several extensions that unnecessarily defined custom JavaScript/CBOR transformation procedures. I fixed them all as part of fixing #738 , which was assigned to me. PR #765 was available for review for some time and fixed all of these extensions. @nadalin mentioned that there was a question on today's call about how the JavaScript/CBOR transformations should be done. Generic transformations were defined by PR #789 and work correctly for this extension, in particular. See them at end of the section at https://w3c.github.io/webauthn/#extensions . (@agl - despite our earlier discussion, because the generic transformations for locations are always in the CBOR -> JavaScript direction, they are always correct; no matter what CBOR number type was in the CBOR, it always becomes a double in JavaScript. We had the particulars of this wrong in our earlier discussion of the handling of this extension.) -- GitHub Notification of comment by selfissued Please view or discuss this issue at https://github.com/w3c/webauthn/issues/800#issuecomment-365810670 using your GitHub account
Received on Thursday, 15 February 2018 02:42:20 UTC