Page MenuHomePhabricator

Text field doesn’t respond to "backspace" key or to arrow keys when writing the comment for the edit
Closed, ResolvedPublic

Description

Author: eliashedberg

Description:
Steps to reproduce

  1. Edit an article
  2. Click "Save page" to save the changes
  3. Write something in the text area where you can comment on your edit
  4. Press the left arrow key to step left in the text

Expected behaviour
5a) The text cursor moves to the left in the text.

Actual behaviour
5b) The text cursor stays at the end of the text.

Further steps to reproduce

  1. Press the "backspace" key

Expected behaviour
7a) The letter to the left of the cursor is deleted

Actual behaviour
7b) Nothing changes

Other observations
I) It is possible to insert text at an earlier part of the text by placing the cursor there with the mouse.
II) It is possible to highlight text with the mouse and replace it by typing (but deletion is not possible).

Is it reproducible?

  • I tried reproducing it when writing this bug report and failed (both arrow keys and "backspace" key worked). I don’t know if this is because the error was very temporary and local (but yet very tangiable) or because I actually did some other steps to invoke the bug but just didn’t realise/notice them.

Environments where the bug occured (might occur in others too):

  • Chrome 29.0.1547.57 running in OS X 10.6.8

Version: unspecified
Severity: normal
OS: Mac OS X 10.6
Platform: Macintosh

Details

Reference
bz53332

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:49 AM
bzimport added a project: VisualEditor.
bzimport set Reference to bz53332.

andlarspam wrote:

I got the same error when updating http://en.wikipedia.org/wiki/Posterior_horn.
When i went back and made another change the error did not occur. I havent found what i did diffrently the second time.

Envirements:

  • Firefox 23.0.1 on windows 7 with service pack 1.

This is bug 50722, which is known to affect Firefox on all OSes. The report in Chrome though I think is new. I'll note that there.

  • This bug has been marked as a duplicate of bug 50722 ***