Last modified: 2014-03-21 00:05:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59551, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57551 - VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list
VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twic...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
PC Windows 7
: Unprioritized normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-25 18:41 UTC by Elitre
Modified: 2014-03-21 00:05 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
This is where the cursor shows up in the text (23.01 KB, image/png)
2013-11-25 18:41 UTC, Elitre
Details

Description Elitre 2013-11-25 18:41:05 UTC
Created attachment 13899 [details]
This is where the cursor shows up in the text

Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=41064, or not.

1. Reach https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=583262564 .
2. Put the cursor after the last reference.
3. Hit Enter once. A new bullet is correctly added.
4. Hit Enter again.

Possible outcomes:
1) see screenshot: the cursor blinks between two lines, on the word "cognitive" (observed in Chrome, Vector/Monobook);
2) the cursor is attached to the top right corner of the picture of Emily Deschanel (Firefox, Vector);
3) the cursor is nowhere in sight (Firefox, Monobook).

Notice that if you repeat the procedure at this point, it will work in Chrome, it will still fail in FF.
Comment 1 Elitre 2013-11-25 18:44:44 UTC
(Sorry, please read, "it will work in Firefox, it will still fail in Chrome".)
Comment 2 James Forrester 2014-03-21 00:05:38 UTC
This was fixed a couple of weeks ago in the HandleEnter re-write work, I think.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links