Ctrl + Shift + T shortcut does not work
Reopen closed tabs DOES work if I do it by hand (right click -> Undo Close Tab). But when I type Ctrl + Shift + T, it opens an empty tab (as if I had typed Ctrl + T).
For the record I'm using Mozilla Firefox 71.0 on Linux Mint 19.2 I have this issue on three different computers with the same distro, so I suppose this is a common issue?
Tất cả các câu trả lời (8)
Do other shortcuts that use Ctrl+Shift as the modifier keys work such as Ctrl+Shift+B for the Bookmark Manager or Ctrl+Shift+H for History sidebar?
Try the Firefox version from the official Mozilla server if you currently use a version from the repositories of your Linux distribution.
d.mattera said
Do other shortcuts that use Ctrl+Shift as the modifier keys work such as Ctrl+Shift+B for the Bookmark Manager or Ctrl+Shift+H for History sidebar?
On the firefox I have, those are accessed with Ctrl + B and Ctrl+ H. But you're right! Shortcuts like Ctrl + Shift + P for private navigation or Ctrl + Shift + A for add-ons don't work either. On the other hand, using Shift for writing with capital letters WORKS FINE as you can see. Do you think it is caused by firefox, or by my OS? I do use shortcuts with Shift on my other software, and this is a first.
cor-el said
Try the Firefox version from the official Mozilla server if you currently use a version from the repositories of your Linux distribution.
I just tried that. Same issue on both.
Do you see the Ctrl+Shift+T keyboard in the History menu in via the Library toolbar button ?
- History -> Recently Closed Tabs/Windows
Can you take a look at the following:
- type "about:config" into your address bar (without quotes) and hit enter
- read & accept the warning
- type "ui.key." into the page's search box
- Let us know what the values are for the following settings:
- ui.key.accelKey
- ui.key.contentAccess
- ui.key.chromeAccess
- ui.key.generalAccessKey
- ui.key.menuAccessKey
Được chỉnh sửa bởi d.mattera vào
d.mattera said
Can you take a look at the following:
- type "about:config" into your address bar (without quotes) and hit enter
- read & accept the warning
- type "ui.key." into the page's search box
- Let us know what the values are for the following settings:
- ui.key.accelKey
- ui.key.contentAccess
- ui.key.chromeAccess
- ui.key.generalAccessKey
- ui.key.menuAccessKey
ui.key.accelKey 17 ui.key.chromeAccess 4 ui.key.contentAccess 5 ui.key.generalAccessKey -1 ui.key.menuAccessKey 18 ui.key.menuAccessKeyFocuses true
cor-el said
Do you see the Ctrl+Shift+T keyboard in the History menu in via the Library toolbar button ?
- History -> Recently Closed Tabs/Windows
I am able to access the recently closed tab via the History menu, and open some of them. But "Ctrl + Shift +T" is nowhere to be seen in the menu, if that's what you mean.
Được chỉnh sửa bởi Cydouzo vào
You would normally see the "Ctrl+Shift+T" access key appended to the first entry in "History -> Recently Closed Tabs" and "Ctrl+Shift+N" appended to the first entry in "History -> Recently Closed Windows". If you see entries in these lists then this means that the undo/restore feature is working and that only the keyboard shortcut is not working.
cor-el said
You would normally see the "Ctrl+Shift+T" access key appended to the first entry in "History -> Recently Closed Tabs" and "Ctrl+Shift+N" appended to the first entry in "History -> Recently Closed Windows". If you see entries in these lists then this means that the undo/restore feature is working and that only the keyboard shortcut is not working.
The Ctrl+Shift+T shortcut is nowhere to be seen. I can see the Ctrl+Shift+N shortcut though, and the shortcut does work fine. On the other hand Ctrl+Shift+P and Ctrl+Shift+A are both on the menu (in front New Private Window and Add-ons respectively), but the shortcuts don't work (it triggers Ctrl+P and Ctrl+A instead). Isn't that fucked up?!
Now the "Restore Tab" feature in itself does work fine, as stated in my original post.
Also, I just tried on yet another computer (same version of firefox, running under Ubuntu 18 this time) and the issue is the same. And I've had this issue for over a month now. I'm surprised it has not already been widely reported.