Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User activation #241

Closed
marcoscaceres opened this issue Jun 21, 2024 · 2 comments
Closed

User activation #241

marcoscaceres opened this issue Jun 21, 2024 · 2 comments

Comments

@marcoscaceres
Copy link
Member

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.

@nsatragno
Copy link
Member

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.

@marcoscaceres
Copy link
Member Author

Ok, cool. Will handle it there and go see about the magic sauce. Maybe we can upstream that to HTML.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants