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”.

Saznaj više

Why doesn't my tab button on the keyboard work since upgrading to FF 16.0?

  • 3 odgovora
  • 2 imaju ovaj problem
  • 3 prikaza
  • Posljednji odgovor od tdmoore2

more options

Noticed this when trying to move on your website, GMail etc so that I can move from field to field (example: To field in Gmail, hit tab button on keyboard to move to Subject field). Tab button non responsive. Safari and Chrome still have this ability. Obviously something has occurred as I upgraded today to 16.0 and yet I was fine in 15.x.

This key is important for speed for daily work. Please advise how I can re-activate it's functionality.

Thank you.

Noticed this when trying to move on your website, GMail etc so that I can move from field to field (example: To field in Gmail, hit tab button on keyboard to move to Subject field). Tab button non responsive. Safari and Chrome still have this ability. Obviously something has occurred as I upgraded today to 16.0 and yet I was fine in 15.x. This key is important for speed for daily work. Please advise how I can re-activate it's functionality. Thank you.

Izabrano rješenje

cor-el,

Just updated tonight to 16.0.1 and voila, issue has been fixed without getting too technical.

Wanted to thank you for your assistance.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (3)

more options

See:

Note: In OS X (as of 2005-01), if this preference is not explicitly set, the “Full Keyboard Access” setting in System Preferences will be honored. All builds before that date (e.g., Firefox 1.0.x) will ignore that setting.
This pref doesn't exist by default, so if you want to use it instead of the system settings then you need to create a new Integer pref with the name accessibility.tabfocus and set the value to what you want (7 is to tab through all the fields).

more options

Thanks cor-el for the reply.

Rephrasing question for you. Why the change in 16.0 then as it was working in 15.x?

To me, this is quite a functional change as all other browsers that I have tested today have the tab key functionality active.

I will work with my IT guy on this reply. Thanks again...and if you know why the change I would be interested in the "why".

more options

Odabrano rješenje

cor-el,

Just updated tonight to 16.0.1 and voila, issue has been fixed without getting too technical.

Wanted to thank you for your assistance.