After Chrome updates, Ctrl+N opens the last-closed window's tabs
Reported by
tabf...@zoho.com,
Sep 13
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Steps to reproduce the problem: Same problem as issue 762951 . Opening a new issue per issue 762951 comment 8. I have now observed the same heisenbug in the first day running each of Chrome 61, Chrome 68, and Chrome 69. This is after a Chrome uninstall/reinstall before Chrome 68. - Open a window and some tabs - Close that window - In an extension popup, hit Ctl+N What is the expected behavior? A new window opens with the New Tab Page I have set (Empty New Tab Page) What went wrong? The window opens with the tabs that were open in the last-closed window. Unfortunately, I still haven't found a reliable repro. However, it is reliably correlated with the update process. After the Chrome 68 update, the problem went away (expected behaviour returned) a day or two after the update. Did this work before? Yes 60 Chrome version: 69.0.3497.92 Channel: stable OS Version: 6.3 Flash Version:
,
Sep 13
,
Sep 13
This seems related to browser startup and/or session restore. If updates are in any way involved, it would only be due to the relaunch done after an update. Such relaunches intentionally perform session restore regardless of the session.restore_on_startup preference. This sort of relaunch can be simulated with chrome://restart. Perhaps this tidbit will help in diagnosing the underlying problem. I wonder how extension popups relate. That's an interesting twist. Removing Internals>Installer.
,
Sep 13
Do you have session restore turned on? If not, did you click an upgrade button in chrome?
,
Sep 14
,
Sep 14
Tried testing the issue on reported chrome #69.0.3497.92 and latest chrome #71.0.3552.2 on windows 10 by following below steps. Steps: ===== 1.Launched chrome. 2.Installed TabFern "https://chrome.google.com/webstore/detail/tabfern-tab-manager-and-b/hbajjpcdbninabigakflkhiogmmjaakm" ( By the reference of issue 762951 comment#8). 3.Opened multiple tabs (~3) in the chrome. 4.Closed the window. 5.Opened new window by hitting Ctrl+N(using the keyboard) in popup extension. 6.Observed a new fresh window. Attached screencast for reference. @reporter: Could you please review the attached screencast and let us know if anything is being missed here. If possible request you provide screencast of the issue so that it would be really helpful for better triaging of the issue. Thanks.!
,
Sep 23
All, thank you for your suggestions and patience. I can reliably trigger the behaviour I am observing with a browser relaunch in Chrome 69. I am triggering the relaunch by changing the top-chrome setting in chrome:flags at the moment. I will try chrome:restart, and will post a screencast as soon as I learn how to make one :) .
,
Sep 23
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 24
Not a screencast, but here's the repro that is working for me. Full Chrome version info attached in case you need it. Repro: - In chrome:extensions, turn off all extensions and apps. - In chrome:settings, make sure that "On startup" is set to "Open the New Tab page." - Download the attached 883709.tar.xz - tar xvJf 883709.tar.xz You will get a `public/` directory. (Note: source is at https://github.com/cxw42/TabFern/tree/883709 . You can git clone / npm install / npx brunch b to build the public/ tree.) - In chrome:extensions, load the public/ directory as an unpacked extension. A popup will appear in the upper-left corner. - Open a second tab next to chrome://extensions and navigate to any web site. (I have tried this with https://demozoo.org and with this issue page.) - Make sure the only Chrome windows you have open are the one with the two tabs, and the popup. - In the second tab, go to chrome://restart . Chrome will restart. - When Chrome reopens, cancel the "disable developer mode extensions" box. - You should now be back where you were: the two-tab window and the popup are open. This is the expected behaviour of a restart. - Close the two-tab window (I get the same results from Alt+F4 and from the "X" on the window frame). - Click on the popup if it isn't already focused. - Hit Ctrl+N. - A window will open. The opening will be logged in the popup. The two previously-open tabs will reappear. The popup will show, in bold, "expected 1 tabs; got 2 tabs." This is the behaviour I have been seeing. What I expected was for the new window to have only one tab, showing the New Tab page. - You can do this any number of times with any number of tabs. After you close the only non-popup window, when you hit Ctrl+N in the popup, it will restore that window's tabs. Boldface lines in the popup mark unexpected behaviour. - Close all Chrome windows and verify no Chrome processes are running. - Launch Chrome. - Open two tabs as above, so the only Chrome windows open are a two-tab window and the popup. - Close the two-tab window as above. - Hit Ctrl+N in the popup. - You will get a window with only one tab, a New Tab page. This is the expected behaviour. - Go to chrome://restart - When Chrome comes back up, the undesired behaviour is back. That is, if you close the only non-popup window and then hit Ctrl+N from the popup, that window's tabs will be restored.
,
Sep 24
tabfern@ Thanks for the feedback... Tried to load the extension that provided in the comment #9, " 883709.tar.xz " and " https://github.com/cxw42/TabFern/tree/883709 " As we are getting error while load the extension. Attached screenshot for reference. Steps: ----- 1. Launched reported chrome 2. Downloaded given extension and tried to load the extension from chrome://extensions/ ,As we are getting error as attached screenshot 3. Tried with the extension mentioned in the comment #6 by following the steps given in the comment #9, As we are unable to reproduce the issue from our end on reported chrome 69.0.3497.100 on comment #9 using Windows 10 and 7. @Reporter : It would be really helpful if a sample Extension is provided, so that we can investigate the issue further and if possible provide screen-cast for better triaging it. Thanks.!
,
Sep 24
Phanindra, thanks for trying! - Do you still see the load error if you load ~\Downloads\TabFern-883709\public instead of ~\Downloads\TabFern-883709? See attached screenshot of a configuration that successfully loaded for me. On Windows, I have to expand the "public" folder, not just select it, for Chrome to use that directory. - I tried the repro from scratch this morning on a Win8.1 machine with the same results (yesterday's tests were on Win7). - It makes sense that you would like to see a screencast. I will put one together as soon as I have time. Yesterday I was able to test and to develop the #9 extension, but unfortunately did not have time to make a clean recording.
,
Sep 24
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 25
tabfern@ Thanks for the feedback... As per comment #11, Tried to enable extension but we are unable to find public folder. Could you please check the attached screen cast and please let us know if anything missed from our end and if possible provide any other sample extension file for further investigation on this issue. Attaching screencast for reference. Thanks..!
,
Sep 25
Phanindra, my apologies for the confusion. The GitHub repo is the source, but not the built version. Attached is the built version from the .tar.xz file, repackaged as a zip with files at the top level, and the screencast you requested. Please use only the attached ZIP for testing. Towards the end of the screencast, after focusing the popup window, I hit Ctrl+N as described in comment 9. I don't have a good way to show that in the screencast, but that is what was happening. Thanks!
,
Sep 25
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 26
tabfern@ Thanks for the feedback.. As per comment #9 and comment #14, as we are able to reproduce the issue on reported chrome version 69.0.3497.92 also on latest chrome 71.0.3562.0 using Mac 10.13.6, Ubuntu 14.04 and Windows 7. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks! |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by tabf...@zoho.com
, Sep 13