Issue metadata
Sign in to add a comment
|
Console history is not saved after tab closing
Reported by
vsemozhe...@gmail.com,
Jun 13 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3128.0 Safari/537.36 Steps to reproduce the problem: 1. Open http://example.org/ and run in the Console: 1+1 You will get '2'. 2. Reload the page and press UP ARROW key in the Console. You will see '1+1'. 3. Do not close the page. Open a new tab with http://example.org/ and press UP ARROW key in the Console. You will see '1+1'. 4. Close all pages with http://example.org/. Open a new tab with http://example.org/ and press UP ARROW key in the Console. You will see one of the older commands. What is the expected behavior? Console history is saved in the last case. What went wrong? Console history is not saved in the last case. Did this work before? Yes This works as expected at least in the 61.0.3124.10 dev (64-bit). Chrome version: 61.0.3128.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: 26.0.0.126 This suspiciously consists with the https://bugs.chromium.org/p/chromium/issues/detail?id=732788
,
Jun 14 2017
,
Jun 14 2017
,
Jun 14 2017
Tested this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 with chrome #61.0.3128.0 as steps mentioned in comment #0 Observed console history is saved as expected. Attaching the screen-cast for reference. vsemozhetbyt@ could you please look into it and let us know any steps i have missed while reproducing the scenario. Thank You...
,
Jun 14 2017
It is strange, but today I also cannot reproduce this issue with the 61.0.3129.0. I will check the behavior a bit more and let you know. Your test seems to consist with my initial one.
,
Jun 14 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 15 2017
Unable to reproduce this issue on Windows 10 with Chrome Canary #61.0.3130.0 as per steps in comment #0. As this bug is inconsistent, removing "Needs-Bisect" label for now, will add again once we have consistent steps to repro this issue. Requesting "DevTools" dev team to look into it for further triage.
,
Jun 19 2017
Unable to reproduce this issue on Windows 10, Mac 10.12.5 and Ubuntu 14.04 with chrome #61.0.3134.0 vsemozhetbyt@ could you please help us with the consistent steps or sample html test case, for further triage. Thank You...
,
Jun 19 2017
Sorry, I was trying to make a stable case but have found it very flaky. Feel free to close.
,
Jun 19 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 19 2017
FWIW, in my #61.0.3134.0 all console memory is wiped out. Probably connected with https://bugs.chromium.org/p/chromium/issues/detail?id=732788#c13
,
Jun 19 2017
Closing because unable to produce a stable repro. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vsemozhe...@gmail.com
, Jun 13 2017