20975 2013-02-12 12:24:50 +0000 [WebDriver Spec]: Undefined behaviour for Cookie setting against a Session that has had no Navigation yet 2014-07-21 23:45:59 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC All RESOLVED FIXED P2 normal --- 20860 1 detronizator simon.m.stewart dburns metanata4 mike public-browser-tools-testing oldest_to_newest 82987 0 detronizator 2013-02-12 12:24:50 +0000 There is a corner case not covered in the Cookies section of the document (https://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html#cookies). When a WebDriver Session is first created, the Browser Window is "domain less". Most probably pointing at "about:blank" or some similar page. The operation to SET/ADD a Cookie allows, in the input object, allows to omit the "domain" field. Current implementations of the specs "silently fill" the domain field for the user, with the domain of the current page. There is a corner-case scenario though. When a new Session, still "domain less" (see above), cannot "fill" that "domain" field if an attempt to set a cookie without domain is made. Current implementations behaviour: - ChromeDriver: throws an error "Couldn't set cookie" - FirefoxDriver: accepts and sets the cookie, and it's available for retrieval - GhostDriver: accepts the cookie, but it's not available for retrieval Hence, it's important to define what should ACTUALLY happen in this scenario. SUGGESTION: ChromeDriver behaviour is correct. Setting a cookie on a "domain less" page should be forbidden and throwing an error/exception. 101394 1 detronizator 2014-02-25 20:00:40 +0000 Glad to see this has been assigned to Simon. @Simon: what's the initial thought on this? 109153 2 dburns 2014-07-21 23:45:59 +0000 https://dvcs.w3.org/hg/webdriver/rev/2964b4c64afa