- From: Mike West via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Apr 2017 08:50:08 +0000
- To: public-webauthn@w3.org
If Microsoft is aiming to lock something down in WD-05 that they want to ship, then I'd suggest that this issue is actually somewhat important. It would be unfortunate if Edge shipped `ScopedCredential` and everyone else shipped `PublicKeyCredential` (or whatever). I do not have strong opinions about the naming, but I do have the strong opinion that we should have the same name across user agents. Given that, is CR an appropriate milestone? Will Edge commit to aligning to any naming changes between now and then? :) FWIW, I _think_ naming changes are pretty trivial in terms of their impact on browser code (in Blink, we'd rename some `.idl`, `.h`, and `.cpp` files, and do some global search-and-replacing), but I've heard on previous calls that these might not be as trivial as I imagine in other browsers. Hammering this out sooner rather than later seems prudent. /cc @AngeloKai -- GitHub Notification of comment by mikewest Please view or discuss this issue at https://github.com/w3c/webauthn/issues/406#issuecomment-297944337 using your GitHub account
Received on Friday, 28 April 2017 08:50:14 UTC