You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -4,3 +4,5 @@ Sketching an asynchronous JavaScript cookies API for documents and workers
At present the best starting point for understanding this API is [the explainer](explainer.md). This API is inspired by and loosely based on the discussion at https://github.com/slightlyoff/ServiceWorker/issues/707 and [elsewhere](https://github.com/WICG/async-cookies-api/issues/14).
The [document-based polyfill](cookies.js) runs best in an `https` page [🔒](https://wicg.github.io/async-cookies-api/cookies_test.html) - the polyfill is also usable but some [tests](cookies_test.js) fail when run in an unsecured `http` page [🔓](http://wicg.github.io/async-cookies-api/cookies_test.html) due to its reliance on `Secure` cookie access.
There is also a [related WICG discourse thread](https://discourse.wicg.io/t/rfc-proposal-for-an-asynchronous-cookies-api/1652).
