8822 2010-01-26 23:44:11 +0000 should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. 2010-10-04 13:58:56 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-document-cookie P3 normal LC 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31259 0 contributor 2010-01-26 23:44:11 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-document-cookie Comment: should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. Posted from: 216.239.45.4 31941 1 ian 2010-02-14 03:49:23 +0000 This would imply that an XHR doc could have cookies set on it, but I can't find any UAs that allow that. See also: https://bugs.webkit.org/show_bug.cgi?id=32115 32077 2 annevk 2010-02-14 12:03:00 +0000 Per http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#document-response-entity-body XMLHttpRequest returns the empty string for cookie but only for non same-origin documents. It should always return the empty string however because we also disallow access to Cookie headers. And setting should just be ignored. I would prefer it if HTML5 could define this so all .cookie information is self-contained. 32348 3 ian 2010-02-18 05:47:09 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with all the above comments. 32349 4 contributor 2010-02-18 05:49:15 +0000 Checked in as WHATWG revision r4778. Check-in comment: Redefine how .cookie is handled. http://html5.org/tools/web-apps-tracker?from=4777&to=4778