- From: David Waite via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Jan 2020 08:53:30 +0000
- To: public-webauthn@w3.org
> But in the meantime, the presence of the "lightning" value in the spec creates confusion. The "lightning" value is in the wild. I do not believe merely removing the line from the spec would compel other clients to stop publishing the value, or compel relying parties to stop relying on the value. I hope the need for it goes to zero over time, but I suspect other browsers will continue sharing "lightning" as a transport for these particular keys even past that point. As I understand it, the point in question to resolve is whether there is more confusion by having "lightning" as part of a master list of known production transports in this specification, or to have developers search other sources not maintained by the W3C when they encounter it. -- GitHub Notification of comment by dwaite Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1294#issuecomment-575049113 using your GitHub account
Received on Thursday, 16 January 2020 08:53:32 UTC