- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Feb 2018 00:21:33 +0000
- To: public-webauthn@w3.org
Yes, I don't think we need to hold up CR for this. Considering that we've not observed any interoperability issues with this despite the importance of these fine details, I'm thinking it seems to be unambiguous enough. Also, I'll retract my previous idea of eliminating the reference to the ECMAScript API. I think it probably is best to keep that, so we don't have to repeat a definition of how to serialize the JavaScript object to JSON. Considering the discussion in #813 and that noone seems to have a concrete proposal for how this should be fixed/improved, I'm leaning towards closing this as not (currently) actionable. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/712#issuecomment-368177185 using your GitHub account
Received on Saturday, 24 February 2018 00:21:40 UTC