452127 - Page Up & Down don't work properly inside a contenteditable DIV

Status: NEW

(Core :: DOM: Editor, defect, P5)

Description

[Robbie Paplin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: 

The page listed above has a 2 DIVs with a contenteditable = true attribute. The
DIV contains several spans with a contenteditable = false attribute. When I set
the caret to an editable region inside the Cc field (a/k/a DIV with
contenteditable = true), and press the Page Up or Page down key, the
caret doesn't move to beginning or the end of the field like I expect it
should.

Reproducible: Always

Steps to Reproduce:
1. Set the caret to the semicolon between Tony Romo & Brett Farve in the Cc... field (via mouse click)
2. Press the Page Up key
3. Note where the caret moves to
4. Set the caret to the semicolon between Tony Romo & Brett Farve in the Cc... field (via mouse click)
5. Press the Page Down key
6. Note where the caret moves to

Actual Results:  
At step 3, the caret moves between Tom Brady & Peyton Manning inside the To Field.
At step 6, the caret moves to the end of the document.

Expected Results:  
At step 3, the caret should stop moving at the beginning of the contenteditable DIV (aka before the first name / Tony Romo).
At step 6, the caret should stop moving at the ending of the contenteditable DIV (aka after the last name / Brett Farve).

The caret should keep moving toward the beginning or the ending of the contenteditable div until it is at the beginning or the ending of the contenteditable div. After reaching the div boundary, additional page up or page down key events should be ignored (like a <input type=text> or <textarea> element would act). In no case should the caret leave the contenteditable DIV.

This is related to Bug 435967.

On IE it works as expected.

Comment 1

[Robbie Paplin]

Attachment: Page that shows caret doesn't handle Page Up / Page Down correctly inside contenteditable DIV

Comment 2

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.