- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Jul 2018 20:47:14 +0000
- To: public-webauthn@w3.org
@akshayku > We always do DOM exception. We also tried Chrome which always returned DOM exception in our testing. do you mean "returned DOM exception" as a result of calling [`navigator.credentials.create()`](https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create) and/or [`navigator.credentials.get()`](https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get) (as opposed to directly calling the webauthn algorithms)? @selfissued the original issue is pointing at an impedance mismatch between [credman](https://w3c.github.io/webappsec-credential-management)'s expectations and what the webauthn algs return. In reviewing credman's [`[[Create]](options, sameOriginWithAncestors)`](https://w3c.github.io/webappsec-credential-management/#dom-credential-create-slot) and [S 2.5.4. Create a Credential](https://w3c.github.io/webappsec-credential-management/#algorithm-create), the former is expected by the latter to return `null` if no credential is created. Similarly for [`[[DiscoverFromExternalSource]](options, sameOriginWithAncestors)`](https://w3c.github.io/webappsec-credential-management/#dom-credential-discoverfromexternalsource-slot) and [S 2.5.1. Request a Credential](https://w3c.github.io/webappsec-credential-management/#algorithm-request) where the latter expects the former to to return `null` if no credential is available. so I do not think we can simply close this. -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/876#issuecomment-407890047 using your GitHub account
Received on Wednesday, 25 July 2018 20:47:30 UTC