- From: Mike West <notifications@github.com>
- Date: Mon, 02 Jul 2018 01:08:14 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 2 July 2018 08:08:36 UTC
Hey, @hadleybeeman! I agree that we should work through the ways in which `document.cookie` does strange things. I don't really think that's in the IETF's scope, however. The cookie RFC defines the storage mechanism (to some extent), and the HTTP-based delivery mechanism. It does not define the `document.cookie` interface (nor, as @annevk notes, does it do a good job explaining what the `document.cookie` interface actually does). One of the things on my list with RFC6265bis is to go through the places in which browsers' behavior diverges from RFC6265, and to adjust the specification accordingly. I haven't taken the time to do that work. I'm hopeful it'll get done this year, but it's not going to get done this quarter. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/290#issuecomment-401705370
Received on Monday, 2 July 2018 08:08:36 UTC