Pnned tabs not restored when window closed but app not shut down
Reported by
firstson...@gmail.com,
Sep 25 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome with a single window. 2. Pin any number of tabs 3. Quit Chrome (without closing windows) 4. Start Chrome (tabs are restored, expected) 5. Close window (do not quit Chrome) 6. Click on Chrome icon (in Dock or wherever), like you're starting it or switching to it. (a new window with a single unpinned tab appears) What is the expected behavior? I expect my pinned tabs to be restored as if I had quit Chrome. Closing the only window should have the same behavior as quitting the application so that when a window is shown again, any pinned tabs are restored. What went wrong? The application doesn't behave as I expect. Did this work before? N/A Chrome version: 60.0.3112.113 Channel: n/a OS Version: OS X 10.12.6 Flash Version: This is a considerable problem when running Postman since it keeps Chrome running, even when I try to quit. This results in the window being closed without quitting the application, and my pinned tabs are lost. I can restore them by going to the history and restoring the previous window, but I think restoring them should be the default behavior. I have raised a bug in the Postman repo as well. https://github.com/postmanlabs/postman-app-support/issues/3552
,
Sep 26 2017
Tested the issue on 60.0.3112.113, latest stable 61.0.3163.100 and on latest canary 63.0.3223.8 using Mac 10.12.6 and is reproducible with steps mentioned in comment#0. Observations: After pinning 3 tabs, On quitting chrome and restoring 3 pinned tabs are seen. But when closed window and opened chrome only Newtab page is seen This issue is seen from M50 [50.0.2166.0] . Hence considering this issue as Non-regression and marking as Untriaged for further inputs. NOTE:Issue is not seen in Ubuntu 14.04 and Windows 10
,
Sep 29 2017
This is working as designed - Cmd+w/closing a window is meant to close pinned tabs. After that they are no longer part of the session. Clicking the Chrome icon in the Dock while Chrome is running currently has same effect as Cmd+n or right-click -> New Window. There's no attempt at session restore, which is what reloads pinned tabs (but only when you have "Continue where I left off" set in chrome://settings ). Pressing Cmd+Shift+n may give you a quicker way to restore the closed window with pinned tabs. Similar issues have been raised in the past - e.g. Issue 54508 Issue 637157
,
Oct 2 2017
As a user of Chrome on multiple systems this is very inconsistent. When I close the only window then reopen it, I expect the tabs to be repopulated. This is the behavior in other OSes, and should be in Mac as well.
,
Oct 4 2017
It's the behavior on other OSs, but not other apps on macOS. Safari, TextEdit, Finder, Pages, etc. all treat closing a window as dismissing it forever, but may restore windows if you quit the app with windows open. Regarding your Postman bug, you should be able to "quit" Chrome while Postman is running. Chrome will stay in the Dock, but all of your Chrome windows will close as if you quit, and they'll come back if you launch Chrome (e.g. by clicking its Dock icon). It's a little bit unusual UI-wise, but it should help in this case. Let me know if it does/doesn't work, or if you still think Chrome's behavior is wrong. |
||||
►
Sign in to add a comment |
||||
Comment 1 by nyerramilli@chromium.org
, Sep 26 2017