history.pushState does not read cookies from same origin
Reported by
nassahaw...@gmail.com,
Mar 31 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: 1) Host the files provided in the attachment in the same domain. 2) Navigate to site1.html and push the create cookie button. 3) Navigate to site2.html and push "print site1 cookies" What is the expected behavior? It should show the cookies pushed from site1 (the output is on the console). What went wrong? It does not. Did this work before? No Chrome version: Version 57.0.2987.110 Channel: n/a OS Version: 6.3 Flash Version: Shockwave Flash 25.0 r0 It does not work on Firefox and Safari either. Works on Internet Explorer, though.
,
Apr 4 2017
Tested the issue on chrome Stable #57.0.2987.133, Canary 59.0.3062.0 in Windows 10.0 & 7 and was able to reproduce the issue. This is a Non-Regression issue since seeing this from M35 #35.0.1898.0, Making the status to Untriaged so that the issue would get addressed. Note : Able to reproduce the issue in MAC 10.12.3 and Linux Ubuntu 14.04. Thank you.
,
Apr 4 2017
,
Apr 7 2017
,
Apr 11 2017
I couldn't find a WHATWG spec text to do this behavior, and since current behavior matches what other browser does, I'd like to mark this WONTFIX. https://html.spec.whatwg.org/multipage/browsers.html#dom-history-pushstate |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ranjitkan@chromium.org
, Apr 3 2017