Join the AMA (Ask Me Anything) with Firefox leadership team to talk about Firefox priorities in 2024. Mark your calendar! Thursday, June 13, 17:00 - 19:00 UTC.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Learn More

Is recent tab cycling behavior changed?

  • 2 odgovora
  • 0 ima ovaj problem
  • 8 prikaza
  • Posljednji odgovor od kktlnx

more options

I want to know if there was any changes in recent tab cycling behavior? Now I need not press enter or click mouse button on one tab from list. Before there was instant tab changing after stop pressing keys (ctrl+tab). Greetings Kamil Tomicki

I want to know if there was any changes in recent tab cycling behavior? Now I need not press enter or click mouse button on one tab from list. Before there was instant tab changing after stop pressing keys (ctrl+tab). Greetings Kamil Tomicki

Izabrano rješenje

I know what the problem was. I have caps lock mapped to ctrl on my Gnu/Linux machine. But when the tab cycling is switched to 'recently visited' mode ctrl and caps lock works differently. Ctrl + Tab works as expected, but caps lock (mapped to ctrl) work in different way (pop up shows up but you need to press LPM or enter to select certain tab, not just release shortcut buttons), so I think firefox ignore that mapping and treat caps lock as caps lock in this particular case.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (2)

more options

'*Now I need to press'

Izmjenjeno od kktlnx

more options

Odabrano rješenje

I know what the problem was. I have caps lock mapped to ctrl on my Gnu/Linux machine. But when the tab cycling is switched to 'recently visited' mode ctrl and caps lock works differently. Ctrl + Tab works as expected, but caps lock (mapped to ctrl) work in different way (pop up shows up but you need to press LPM or enter to select certain tab, not just release shortcut buttons), so I think firefox ignore that mapping and treat caps lock as caps lock in this particular case.