- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Feb 2018 19:56:33 +0000
- To: public-webauthn@w3.org
> In thinking about @agl 's comments some more, one of my concerns is that if browsers don't implement the ability for RPs to call new extensions that the browsers don't yet understand, it will stifle innovation, as authenticator vendors won't be able to implement new extensions and have RPs have any way to use them. On this topic (and thinking out aloud: this is not a commitment on Chrome's part) we could overload the current enterprise policy that we have for allowing attestation without a prompt to also enable extension pass-through on a per-RP basis if groups wish to develop extensions. However, I'm not sure that it's crazy that groups doing extension development build a custom Chromium or Firefox build to add support for there experimental extension. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/pull/789#issuecomment-365042879 using your GitHub account
Received on Monday, 12 February 2018 19:56:44 UTC