- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 18:29:24 +0000
- To: public-webauthn@w3.org
This seems like a Chrome bug report? As such, I don't think it applies here. The reason that extensions in Chrome cannot call Webauthn is because they don't have standard domains, and WebAuthn is based around RP IDs. Chrome does not have any plans to change this at the moment and it's not clear how extensions could be mapped into WebAuthn's RP ID space. You might want to open a Chrome bug on this, but I don't think it would be considered in the near team. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1158#issuecomment-463312412 using your GitHub account
Received on Wednesday, 13 February 2019 18:29:26 UTC