-
Notifications
You must be signed in to change notification settings - Fork 65
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
Feedback: User Activation unpredictable for IndexDB loaded handler permissions #246
Comments
I got the same problem here |
I'm not the expert on what counts as user activation, but generally that involves the user interacting with the page itself; I don't think dialogs such as window.confirm() necesarilly count for that. whatwg/html#3849 tries to more accurately specify what counts as user activation. In general the HTML spec is probably the better place to discuss what the model behind user activation should look like, while the chromium bug tracker would be better for specific issues with the chrome implementation of it. |
Hi there. I use
window.confirm()
opening dialog with an Angular app that allows the user to give permission (again) for the last used file handler loaded from IndexDB, but the behavior of the user activation is inconsistent.Sometimes one click on the confirm dialog is enough to activate it and successfully pull up the FileSystem permission dialog.
Other times, it requires more mouse events to do that or simply throws
Error: User activation is required to request permissions.
Is there a clear guideline as to how to meet the user activation requirement before making the permission requests?
Otherwise, it's hard to implement an opening dialog the needs permission requests. Thanks.
The text was updated successfully, but these errors were encountered: