Can not select image when navigating text with arrow keys.

[Joe Kavanagh]

1. Add some text, insert an image, and add some more text after the image.
2. Using the left arrow key move the cursor back to select the image.

Observe that the cursor by-passes the image an moves to the text before the image. This prevents the user from opening the image context menu using the keyboard.

[Joe Kavanagh]

This is also occurring for flash objects.

[Frederico Caldeira Knabben]

This may be a browser limitation. We need to check if it's possible to workaround it.

[Garry Yao]

@fred That's exactly what been proposed these days at Mozilla.
​https://wiki.mozilla.org/Accessibility/EditorBehaviourOnUserInput

[Garry Yao]

It's definitely a browser bug, and has appearance on both IE and Firefox (works with Webkit for me right now).
Even worse, this phenomenon happens to every type of control ( checkbox, img, select) in condition that the element is surrounded by text. Most unfortunately, due to #703 and #3069, what been impacted is that SHIFT+ARROW keys/mouse drag will be the only way for selecting such elements in FF3.
Considering the wide affecting of this bug, I'm proposing an fall-back range inspection approach to selection.getSelectedElement to correctly figure out the element underhood.
Then we'll be sitting and looking for the real fix at the browser side.

[Frederico Caldeira Knabben]

Functions like getSelectedElement we extensively used in the editor during its operations. Because of this, we must avoid making DOM manipulations (creating bookmarks) inside of it, being limited to looking at the native selection/range objects to figure things out.

Are we able to fix things on key press instead, like selecting and deselecting the object on arrows press?

[Garry Yao]

Replying to fredck:

Functions like getSelectedElement we extensively used in the editor during its operations. Because of this, we must avoid making DOM manipulations (creating bookmarks) inside of it, being limited to looking at the native selection/range objects to figure things out.

Though it could be proved that selecton:getSelectedElement wasn't really been used *exclusively*, currently, it's only used by some of our dialogs.
I would still like to follow your advice as it's obviously possible for us to complete this task more unobtrusively, without bothering the walker.

Are we able to fix things on key press instead, like selecting and deselecting the object on arrows press?

Managed keystroke should always be our last choice...for this case, we're not only talking about arrow keys, but also mouse drag; And we're not talking only about 'Link' dialog, but all control elements.

Providing a new patch based on Fred's suggestion.

[Frederico Caldeira Knabben]

I would prefer taking more time to this ticket.

[Frederico Caldeira Knabben]

Recent changes, specially [5255], have already fixed this issue.