-
Notifications
You must be signed in to change notification settings - Fork 386
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
Necessity of User Gesture while accessing the storageAccessFor() api #244
Comments
Hi @sreek10, I'm not sure what advice you saw for avoiding the need for a user gesture, but Chrome intentionally requires a user gesture for the first call to However, the user gesture is unnecessary for subsequent calls, after the first one. |
A prompt and a user gesture are different things.
It is possible to avoid the need for a prompt (in Chrome) if all of the sites involved are in the same RWS. It is not possible to avoid the need for (at least one) user gesture. |
I was trying to use the demo mentioned in the related website sets document and implement the same for two of my websites with medscape.com and medscape.org where .com is the primary and later is the associated one.
Every time I initiate the demo using CLI I see the permission is prompt and I have to add a user gesture like button click.
Is there anyway to avoid the same as user gesture for our sites are not possible to integrate and I saw there is one way to avoid the user gesture.
When I tried the mentioned way I am still getting the permission as prompt and user gesture is required to move forward.
Can you please help here.
Thank you
The text was updated successfully, but these errors were encountered: