CTRL-Tab stops cycling in most recently used order
Despite having the setting "Ctrl+Tab cycles through tabs in recently used order" selected, CTRL-Tab has suddenly stopped cycling tabs in the most recently used order. Firefox behaves as if the setting is disabled. This is the third time I've experienced this issue in the past year, and every time the only solution that worked was to create a new profile. It is exhausting to get a new profile back to exactly how the old profile was, and it's something I shouldn't have to do.
Scenario: I am on Windows 11 (though I think this has also happened to me on Windows 10), currently using version 146.0.1 (though this has happened on previous versions). CTRL-Tab cycles in the most recently used order just fine for several months, then it suddenly doesn't—this happens in the middle of an active session, i.e., not after a restart of the browser nor the computer itself. I have four add-ons, none of which control tab cycling, nor have I added/removed any add-ons nor changed any of their settings since their initial installation many months ago.
What I've tried:
- Disabling/re-enabling the setting (even though it is already checked)
- Disabling/re-enabling the config browser.ctrlTab.sortByRecentlyUsed
- Restarting Firefox normally
- Restarting with add-ons disabled—note that the issue persists even with add-ons disabled
- Disabling the setting, then restarting Firefox, then re-enabling the setting
- Restarting the computer
It's the same thing described in this Reddit thread. What else can I try?
Modificado por coderCK a
Todas as respostas (2)
Hi,
this behavior is usually not caused by Firefox itself.
In most cases it’s related to one of the following:
Extensions (especially tab managers, shortcut or gesture add-ons) Please try starting Firefox in Troubleshoot Mode. If the problem does not happen there, an extension is very likely responsible.
Custom settings Changes made in about:config can alter how keyboard shortcuts work. Testing with a new, clean Firefox profile can help rule this out.
Operating system or third-party software Keyboard remappers, window managers, or vendor utilities (AutoHotkey, Logitech/Lenovo/HP tools, etc.) may intercept shortcuts before Firefox receives them.
Also note that some shortcut behaviors have been intentionally changed in recent Firefox versions, so what looks like a bug may actually be expected behavior now.
If the issue does not occur in Troubleshoot Mode or a new profile, then Firefox itself is very unlikely to be the cause.
Hope this helps! Sebastian
Hi Sebastian,
Thank you for taking the time to respond.
Sebastian Becker said
Please try starting Firefox in Troubleshoot Mode. If the problem does not happen there, an extension is very likely responsible.
I tried Troubleshoot Mode, and it did not solve the problem. Even in Troubleshoot Mode, Firefox behaves as if the setting is disabled, and pressing CTRL-Tab moves to the next tab on the right every time.
Custom settings Changes made in about:config can alter how keyboard shortcuts work. Testing with a new, clean Firefox profile can help rule this out.
I have not made any custom settings changes, so this cannot be it either. The only time I changed anything was to troubleshoot this issue by toggling browser.ctrlTab.sortByRecentlyUsed after the issue had already started.
Operating system or third-party software Keyboard remappers, window managers, or vendor utilities (AutoHotkey, Logitech/Lenovo/HP tools, etc.) may intercept shortcuts before Firefox receives them.
While I do use AutoHotkey, I don't use it in Firefox nor do I have anything mapped to CTRL-Tab. Furthermore, that wouldn't explain why it is broken in one profile but working in another profile; if I have both profiles open (by choosing "Launch profile in new browser"), CTRL-Tab works correctly in one but not the other. This indicates that the profile itself is damaged/corrupted/not working properly, and not that a hot key is being intercepted.
Also note that some shortcut behaviors have been intentionally changed in recent Firefox versions, so what looks like a bug may actually be expected behavior now.
I don't believe this is relevant unless the behavior for CTRL-Tab changed recently, and to my knowledge it hasn't (nor would that explain why it would work differently in two profiles using the same version of Firefox).
If the issue does not occur in Troubleshoot Mode or a new profile, then Firefox itself is very unlikely to be the cause.
The issue does occur in Troubleshoot Mode! Also, in my original post I stated that the only way to fix the issue is to create a new profile. To me, this means that somehow the profile is being damaged. Perhaps there's a way to manually fix the profile itself?
Deve iniciar a sessão com a sua conta para responder às mensagens. Por favor, comece uma nova pergunta, se ainda não tiver uma conta.