Did the functionality of Ctrl-Shift-T change?

2,501 views
Skip to first unread message

Reffu

unread,
Jan 6, 2012, 1:17:06 PM1/6/12
to Chromium-discuss
Currently using latest (or almost latest) chromium nightly build
(116480). It used to be that when I closed the browser and reopened
it, hitting ctrl-shift-t would restore the last session I had open (eg
all tabs were restored and the back history for each tab was
restored). Now however, ctrl-shift-t only works for individual tabs
and no longer works after closing the browser. I'm not sure what
version this changed at but has been happening to me for a while. I
was wondering if this was an intentional change on somebody's part or
is just a bug.

I have tried disabling all extensions and reviewing the flags I'm
using but nothing changes. And because I know someone will suggest it
(because they won't read my entire post) I do not want to set chrome
to restore last session on start. I only want to reopen my last
session if I accidently close the browser or need to get back to my
previous tabs quickly.

Thanks

reffu

Ben

unread,
Jan 6, 2012, 1:29:01 PM1/6/12
to nickmar...@gmail.com, Chromium-discuss
Sounds like something I've been experiencing lately. I can actually
restore the tabs from the recently closed menu on the new-tab page, or
with ctrl+shift+t from the new-tab page (or other pages, when no text
fields are selected and no plugins are active--have focus).

However, if I close any tab in the new session, then all the tabs from
the previous session are lost. I used to still be able to press ctrl
+shift+t to restore them, they would just not be in the recently closed
menu anymore, but that no longer works.

Reffu

unread,
Jan 6, 2012, 2:44:32 PM1/6/12
to Chromium-discuss
Actually, i just checked and I can't even restore it from the recently
closed menu. Upon closing the browser and opening it again, the
recently closed menu is not there and does not appear until I close a
tab.

Ben

unread,
Jan 6, 2012, 3:05:20 PM1/6/12
to nickmar...@gmail.com, Chromium-discuss
Ah, looks like the bug I was talking about was fixed in the latest beta
of Chrome. What you're talking about could be either a regression or new
bug, so it might be a good idea to check crbug.com for one that sounds
like yours; star it if you find one, or file a new one at new.crbug.com
if you can't.

Also, whether you create a new bug or star an existing one, please send
a link back to the list so that others can star the bug and receive
updates.

Reply all
Reply to author
Forward
0 new messages