You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@nsatragno, on the Chromium side - with Password and Federated credentials - do you consume the user activation? Also, clearly I think the document should have system focus.
The text was updated successfully, but these errors were encountered:
There's no user activation requirement for password, federated, fedcm, or (normally) webauthn credentials on Chromium. Safari has some special sauce for webauthn where you get a "free" activation when the page is first loaded and need a user gesture to trigger subsequent requests.
The only case I can think of a credman credential consuming a user activation in a standardized way is webauthn in a cross-origin make credential request. I would be inclined to have the digital identity credentials spec handle it itself considering this.
See WICG/digital-credentials#91 ... the question is, should Cred Man deal with user activation requirements?
And if so, should we enforce "fully active descendant of a top-level traversable with user attention"
@nsatragno, on the Chromium side - with Password and Federated credentials - do you consume the user activation? Also, clearly I think the document should have system focus.
The text was updated successfully, but these errors were encountered: