391871 - Double-clicking select the float most far from the double-click area

Status: REOPENED

(Core :: DOM: Selection, defect)

Description

[Martijn Wargers (dead)]

Attachment: testcase

Maybe sort of related to bug 306240.

When I double-click somewhere in the empty area of the block, the float furthest from the double-click are gets selected, which seems a bit strange to me.
Not a big deal, though.

Comment 1

[Kim]

Attachment: testcase #2

The element which get selected is the first child of the box.

I've included a testcase showing that

#1 Double-clicking selects the first word of the first floated child

#2 If there are child elements that are not floated, the closest one of those will be selected instead

#3 Selecting the content of an inline element will also select the content of the the next sibling, if the next sibling are floated and all the following siblings are block elements

Comment 2

[Uri Bernstein]

Note that this only happens when layout.word_select.eat_space_to_next_word=true (i.e. by default on Windows). otherwise, double-click selects nothing in the testcase.

Comment 3

[Kim]

With layout.word_select.eat_space_to_next_word=false and layout.word_select.stop_at_punctuation=true in my testcase above

#1
Double-clicking does nothing
a. Double-clicking+dragging selects the text up to, and including, the space after the comma (,)
b. Double-clicking+dragging selects the text up to the dot (.)
b (with stop_at_punctuation=false).
Double-clicking+dragging selects the text up to the word before the dot (.), 'eating' the space before it.
I get the same behavior with eat_space_to_next_word=true, is it supposed to do this?

#2
No difference

#3
Double-clicking the first 'nofloat' span selects the tabs before it, double-clicking the second 'nofloat' span selects both the tabs before it and the ones after it.
I can't see any reason why the last 'nofloat' span before a block element, or the end, should be treated differently by eating an extra 'word', am I missing something here?