This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Ctrl+Tab not working

  • 4 răspunsuri
  • 4 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de PoignantTuna

PoignantTuna
PoignantTuna
more options

Hello - it seems since the most recent update Ctrl+Tab (go to next tab) is not working, either in Normal or Safe Mode. All other Ctrl functions are working (Ctrl+Shift+T, Ctrl+T etc.).

Hello - it seems since the most recent update Ctrl+Tab (go to next tab) is not working, either in Normal or Safe Mode. All other Ctrl functions are working (Ctrl+Shift+T, Ctrl+T etc.).

Soluție aleasă

Is only Ctrl+Tab and Ctrl+Shift+Tab not working?

Do "Ctrl + Page Up" and "Ctrl + Page Down" work?

Did you try to close and restart Firefox or reboot the computer?

Citește acest răspuns în context 👍 1

Toate răspunsurile (4)

the-edmeister
the-edmeister
  • Moderator
more options

Try the Firefox Safe Mode for troubleshooting this issue.

PoignantTuna
PoignantTuna Deținătorul întrebării
more options

the-edmeister said

Try the Firefox Safe Mode for troubleshooting this issue.

It still isn't working using Safe Mode...not sure how I should further troubleshoot the issue once in that mode.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Soluție aleasă

Is only Ctrl+Tab and Ctrl+Shift+Tab not working?

Do "Ctrl + Page Up" and "Ctrl + Page Down" work?

Did you try to close and restart Firefox or reboot the computer?

PoignantTuna
PoignantTuna Deținătorul întrebării
more options

It seems a reboot did the trick. Apologies for the false alarm and thank you!!!