Application > Cookies: Creating a new cookie sets wrong default domain
Reported by
kdzwinel@gmail.com,
Mar 2 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3026.3 Safari/537.36 Steps to reproduce the problem: 1. Go to google.com 2. Open DevTools, go to Application > Cookies 3. In the same tab and w/o closing DevTools, go to amazon.com 4. Try crating a new cookie What is the expected behavior? Default cookie domain should be amazon.com What went wrong? Default cookie domain is google.com Did this work before? No Chrome version: 58.0.3026.3 Channel: dev OS Version: OS X 10.12.3 Flash Version:
,
Mar 2 2017
,
Mar 8 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b80db6918ca7234bc688efca0e1716bc3aa2c3b5 commit b80db6918ca7234bc688efca0e1716bc3aa2c3b5 Author: kdzwinel <kdzwinel@gmail.com> Date: Wed Mar 08 23:51:28 2017 Show 'inactive' cookies (fix after https://codereview.chromium.org/2714913002 ). Update default domain for the CookieTable whenever target domain changes. BUG= 697779 Review-Url: https://codereview.chromium.org/2726823004 Cr-Commit-Position: refs/heads/master@{#455599} [modify] https://crrev.com/b80db6918ca7234bc688efca0e1716bc3aa2c3b5/third_party/WebKit/Source/devtools/front_end/cookie_table/CookiesTable.js [modify] https://crrev.com/b80db6918ca7234bc688efca0e1716bc3aa2c3b5/third_party/WebKit/Source/devtools/front_end/resources/CookieItemsView.js
,
Mar 13 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by konrad.d...@brainly.com
, Mar 2 2017