[FF] Selection split by widgets should be merged in model to one range

[ma2ciek]

FF split the selection into two ranges because of the contenteditable=false attribute in the widget. This causes two problems. First, the selection that contains multiple ranges is not supported well yet, and second, that we can't select an image element.

[Reinmar]

If we can do that, we would avoid many issues with handling unnecessarily multi-range selections.

Of course, if we'll fix the selection on model->view conversion, then it will be re-rendered and there's a question of what Firefox will do with it. Especially, if we'll re-render the selection while it's being made by dnd.

[scofalik]

This isn't that easy because in FF I cannot drag selection after the image:

When I drag on a "Quote" the selection is not made after the image. Funny, when I drag from "Quote" backwards above the image it works correctly (in DOM - although I expected three ranges and there are two, but they cover the selected area).

I tried to overcome this issue by building a range that covers all ranges in the current selection, but FF has problems with setting selection over nested editable. Look at this fiddle: https://jsfiddle.net/kx2aatd6/2/

It doesn't work, even though you can make such range by placing selection in first paragraph and then holding Shift and clicking in the second paragraph. But even though the selection looks correct, when you, for example, hit Backspace only the range before nested editable and in nested editable are removed. So it doesn't work correctly in this case either.

Do you have any ideas how we could tackle this issue?

EDIT: Another funny thing: when you remove nested editable (just leave the #widget element) selecting through mouse drag works correctly, but selecting by code is still incorrect.

[scofalik]

I had a wrong fiddle previously, updated it: https://jsfiddle.net/kx2aatd6/2/.

[scofalik]

Hmm, it looks like not only Firefox has a problem with such selection... So does Chrome... Or I did something wrong?