386300 - Caret disappears when pressing UP at the top of a contenteditable region

Status: VERIFIED FIXED

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

Description

[Peter Van der Beken [:peterv]]

When pressing UP at the top of a contenteditable region the caret disappears. It should probably go to the beginning of the editable region. Might need a new nsISelectionController implementation for that.

See also bug 237964, comment 70.

Comment 1

[Dan POPA]

(In reply to comment #0)
> When pressing UP at the top of a contenteditable region the caret disappears.
> It should probably go to the beginning of the editable region. Might need a new
> nsISelectionController implementation for that.
> See also bug 237964, comment 70.


Is not that important, but perhaps the caret should remain where it is? Same as in textarea?

Go at the beginning of the editable region on CTRL+Home.
Maybe: CTRL+UP goto to the beginnig of the element (IE like).

Comment 2

[Peter Van der Beken [:peterv]]

This should probably be a blocker. The fact that the cursor disappears make editing very confusing.

Comment 3

[Peter Van der Beken [:peterv]]

Attachment: v1

Goes to the beginning/end of the editable region, which is fairly standard behaviour in editors on Mac and Linux and also what Safari does. It is different from what IE does. Not really sureyet  if we should go with that or not, or make this behaviour platform-specific.

Comment 4

[Peter Van der Beken [:peterv]]

Attachment: v1.1

Pressing up at the top of a textarea moves the cursor to the beginning of the textarea too, so let's go with this. The patch is based on nsTextInputSelectionImpl::CompleteMove.

Comment 5

[[e-mail]]

This broke cmd_moveTop in editor/midas - TakeFocus, and therefore HandleClick, expects its aNewFocus element to have a parent.

Comment 6

[Peter Van der Beken [:peterv]]

Regression from comment 5 is filed under bug 394264. This bug is fixed as filed.

Comment 7

[Tony Chung [:tchung]]

Verified fix on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3) Gecko/2008020418 Firefox/3.0b3.  testcase in comment #3 and #4 is working.