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.

Search Support

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.

Learn More

In latest Nightly, arrow keys don't move the cursor but instead exit the text box. How can I fix this so that the arrow keys move the cursor?

  • 1 odgovor
  • 2 ima ovaj problem
  • 3 views
  • Posljednji odgovor poslao AaronMT

more options

Using Nightly 28.0a1, I'm having a problem with the text box fields when typing. I use Hacker's Keyboard which has onscreen arrow keys and I find it more convenient than fiddling with a tiny cursor thumb when editing text. On the Play Store Firefox it works just fine but on Nightly, any time I try to move the cursor with the arrow keys it jumps out of the text box and highlights other elements on the page. This is annoying beyond belief as it means having to resort to that imprecise thumb cursor that takes forever to get where you want it. Is this a known issue with the latest nightly builds?

Using Nightly 28.0a1, I'm having a problem with the text box fields when typing. I use Hacker's Keyboard which has onscreen arrow keys and I find it more convenient than fiddling with a tiny cursor thumb when editing text. On the Play Store Firefox it works just fine but on Nightly, any time I try to move the cursor with the arrow keys it jumps out of the text box and highlights other elements on the page. This is annoying beyond belief as it means having to resort to that imprecise thumb cursor that takes forever to get where you want it. Is this a known issue with the latest nightly builds?

All Replies (1)

more options

Thanks for the report. I have filed bug https://bugzilla.mozilla.org/show_bug.cgi?id=939959. It would be helpful to know and if you can comment into the bug to indicate which input field you are testing on.

Izmjenjeno od strane AaronMT