731924 - Contenteditable prevents proper arrow key document navigation, resulting in only going to the Top, or Bottom

Status: VERIFIED DUPLICATE of bug 669026

(Firefox :: Untriaged, defect)

Description

[Jeffrey 'jf' Lim]

Attachment: content-demo1.htm

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120217110108

Steps to reproduce:

Load up a page with any divs with the contenteditable attribute set. This happens even if these divs are hidden, and out of sight (either set as "display: none", or some parent container of the div is hidden).


Actual results:

The arrow keys (specifically "up" and "down") no longer work as expected, and end up moving to either the top, or bottom of the document (or even some weird "just below the top" of the document position). I will attempt to describe this last "just below the top of the document position" behaviour, since the markup for this is the simplest, and the easiest to reproduce. If you need more elaboration and markup for the other behaviours, let me know - although I imagine that it should be simple enough to zoom in to the offending code.

For the file that I am attaching, the following behaviour is seen after the document is loaded:

1. press the up / down arrow (doesn't matter which!). The document scrolls down juust a little (this is _not_ the usual amount that it would have scrolled if the contenteditable attribute had not been present... and then the down arrow key pressed)

2. Now, the document remains "stuck" in this scroll position. "Arrow up", "Arrow down", PageUp, PageDown, Home, and End keys fail to change the vertical scroll position of the document.

3. Now I use the mouse to move the scrollbar to ANY vertical position (doesnt matter if the scrollbar is at the absolute top, absolute bottom... or somewhere in between).

4. press the up / down arrow key again (does NOT matter which key!). The document scrolls back to that previously position as mentioned in step 1, and again becomes "stuck" (see description in step 2).


Expected results:

The arrow keys should move a document up and down as per usual, bit by bit.

Comment 2

[Jeffrey 'jf' Lim]

thanks, Alice0775! Can't believe that the duplicate wasn't found.