Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe
Firul de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.
Rezolvat Arhivate

why did Ctrl+LeftArrow and Ctrl+RightArrow key combinations change?

Firefox
dnechodo răspuns
dnechodo
dnechodo

In all versions of Firefox prior to v10, Ctrl+LeftArrow orCtrl+RightArrow while the cursor was in an editable control would cause that cursor to move to the start of the previous or next word, respectively, as is standard in virtually every installation I've seen. Why would the developers of FF10 see fit to violate those standards & cause an inordinate amount of time to be wasted returning to the edit & manually repositioning the cursor???

In all versions of Firefox prior to v10, Ctrl+LeftArrow orCtrl+RightArrow while the cursor was in an editable control would cause that cursor to move to the start of the previous or next word, respectively, as is standard in virtually every installation I've seen. Why would the developers of FF10 see fit to violate those standards & cause an inordinate amount of time to be wasted returning to the edit & manually repositioning the cursor???

Toate răspunsurile (2)

cor-el
cor-el
  • Moderator

Soluție aleasă

No problems here with those keys in Firefox 10.0.2 on Linux.

Start Firefox in Use Troubleshoot Mode in Firefox to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).

dnechodo
dnechodo Deținătorul întrebării

Following the instructions supplied by cor-el, and applying a tiny piece of 'puter logic, I enabled one add-in at a time after starting from 'no add-ins'. When i got to the add-in "Tab Utilities 1.1.3". enabling it brought back the problem. Reviewing the details of its operations confirmed that I'd found the culprit. Henceforth, "Tab Utilites" will no longer be resident on my systems.