Re: [webauthn] Add Signal API (#2093)

@nsatragno I finally caught up on the latest shape of the API. It's almost `isUserVerifyingPlatformAuthenticatorAvailable` again but honestly I find it hard to disagree with the reasoning for it:

- @pascoej made a good point that the two primary reports, `signalAllAcceptedCredentialIds()` and `signalUnknownCredentialId` have diametrically opposite use cases (the former would be sent after a **successful** auth ceremony, while the latter would be sent after **failed** auth ceremony)
- The three discrete methods also addresses @arnar's concern that the old structure _technically_ allowed for multiple reports of the same type to be sent. The new structure definitely reduces edge cases related to this.

I would say I am generally in agreement with the latest shape of the API. I've got some comments I'll leave as Review comments in a few.

-- 
GitHub Notification of comment by MasterKale
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2093#issuecomment-2253571595 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 26 July 2024 22:07:13 UTC