Page MenuHomePhabricator

Cursor position randomly jumps
Closed, ResolvedPublic

Description

Author: ngautam

Description:
While typing, the cursor will jump back some number (usually about 3 to 5) of spots in the text.

This has been, so far, incredibly difficult to reproduce, but has been seen in FF 3.6 for Linux and Mac.

Sometimes it will wait until the user is done typing (indicating possible link to the delayedBind) but other times it will shift *as* the user is typing.


Version: unspecified
Severity: major
URL: en.wikipedia.org and all other wikimedia projects

Details

Reference
bz22440

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.
StatusSubtypeAssignedTask
ResolvedNone
ResolvedNone

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:54 PM
bzimport set Reference to bz22440.

Guillaume's reproducing instructions included pressing Enter at the end of a header line and seeing two blank lines being created. This is also not consistently reproducible, and seems to be linked to the cursor moving issue.

wikibugs wrote:

Was not able to reproduce the defect in all browsers

wikibugs wrote:

Test link : http://prototype.wikimedia.org/deployment-en/
Version : r62215

Tried the scenario on Fire Fox 3.6 on Mac. Was not able to reproduce the same.

I got this when adding section titles: after typing "== foo ==" (or just "== foo =") and pausing for a moment, the cursor jumped to the middle of the opening == just as the toc changed. This happened every time when I added a section title, but I couldn't get it again after a reload. This was the edit in question: http://hu.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=prev&oldid=7190938

(forgot to mention it was FF 3.5/WinXP.)

wikibugs wrote:

Tested link: http://prototype.wikimedia.org/deployment-en/
Version : r62529

Not able to re-produce the bug stated with the given steps. May be because of the bug 22543

ngautam wrote:

fixed with adding <p> classes as TOC markers rather than invisible <divs>