-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Persistent Storage - not supported in Chrome #25707
Comments
This issue was automatically closed because the title was left as the default, and a summary was not added. If this is not a spam issue, please replace the |
Please reopen. |
Could you link to an MDN article or state the feature key for the particular feature you are referring to? |
browser-compat-data/api/Permissions.json Line 666 in 5267372
https://caniuse.com/mdn-api_permissions_permission_persistent-storage https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/persist Basically it is "supporting" a feature by just gracefully refusing any and all attempts to use the feature. |
What type of issue is this?
Other
What information was incorrect, unhelpful, or incomplete?
The persistent-storage permission should not be considered a working feature on Google Chrome.
A mechanism for obtaining the permission simply does not exist. It just returns false. It should not be considered a compliant feature.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
Should not be marked as available.
Did you test this? If so, how?
I tried it on my own https domain, triggered from a user pressed button, and tried again by injecting code to do it through the F12 menu into a https://developers.google.com/ web page. Perusing the internet regarding this feature, it doesn't seem anyone has ever gotten it to work on Chrome.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
The text was updated successfully, but these errors were encountered: