Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

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

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 3 Hecha
  • Mbohovái ipaháva dnechodo

more options

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???

Ñemoĩporã poravopyre

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

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode 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).

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (2)

more options

Ñemoĩporã poravopyre

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

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode 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).

more options

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.