-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove navigator.yieldForStorageUpdates() #334
Comments
As sad as it is, we should probably also remove the storage mutex, replacing it with warnings and examples of how cookies and local/session storage are all highly unsafe due to its lack. And maybe suggesting alternatives, if there are any... |
Yes, we should probably do that as well. Want to lump that into this issue, or a separate one? |
I'll open a new one to contain any controversy there. Removing an unimplemented public API is probably less controversial... |
Also rename NavigatorStorageUtils to NavigatorCookies. Fixes #334
Also rename NavigatorStorageUtils to NavigatorCookies. Fixes #334
Closing this in favor of #335 to keep discussion in a single place. |
Also rename NavigatorStorageUtils to NavigatorCookies. Fixes #334
Also rename NavigatorStorageUtils to NavigatorCookies. Fixes #334
Also rename NavigatorStorageUtils to NavigatorCookies. Fixes #334
https://html.spec.whatwg.org/#dom-navigator-yieldforstorageupdates
Nobody has implemented it, and it's likely anybody ever will, because the storage mutex concept itself hasn't been implemented.
The text was updated successfully, but these errors were encountered: