cookie-store
cookie-store copied to clipboard
Asynchronous access to cookies from JavaScript
*** Preview | Diff
We're considering our options RE `DOMTimeStamp`, and wondering what it's used for. It seems less well-defined than `DOMHighResTimestamp`. Would y'all consider switching over? See heycam/webidl#2 for discussion.
Is there any desire to move the Cookie Store API to WebApps WG? The specification is a part of [WebApps WG charter](https://www.w3.org/2019/05/webapps-charter.html#wicgspecs), and will be shipping in [Chrome in M87](https://chromestatus.com/feature/5658847691669504)....
Following dd2ddc7ce8b081ef10d913fc71b862059d8c1a4f there's this text: > To encode a string, run UTF-8 encode on string. This text is unnecessary, as places that need to encode invoke "UTF-8 encode" directly. We...
I think we should add the following to the `Set a Cookie` section: ``` 1. If |name| contains U+003D (`=`), then return failure. ``` Otherwise, a cookie with a name...
This is mentioned at several places, but AFAIK the only reference is on the IDL: https://heycam.github.io/webidl/#SecureContext which in turn links to https://html.spec.whatwg.org/multipage/webappapis.html#secure-context and in turn to https://w3c.github.io/webappsec-secure-contexts/#potentially-trustworthy-url https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy This seems...
I think I raised this before, but I don't really see text about it in the specification. If you limit yourself to UTF-8, you need to deal with cookies that...
The ["compute the cookie-string from a cookie store"](https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-06#section-5.5) algorithm appears to take a cookie store as an argument, but https://wicg.github.io/cookie-store/#query-cookies doesn't pass one. The choice of this argument might or...
I saw this was initially covered in #36, but I think it's worth revisiting now. https://github.com/WICG/cookie-store/blob/9a100293eb01c0828fea16d266ea6d410ef6934f/index.bs#L497 The default `SameSite` value is `Strict`. We've made the default treatment for cookies elsewhere...
Consider this example: ``` try { await cookieStore.set({ name: 'session_id', value: 'this data will be LOST', expires: 365 * 24 * 60 * 60 * 1000 }); } catch (e)...