1250006 - "DoubleClick a word then drag" doesn't select the word where selection started

Status: RESOLVED WONTFIX

(Core :: DOM: Selection, defect, P4)

Description

[arni2033]

Attachment: testcase 1 - 'DoubleClick then drag' doesn't select the word where selection started.htm

>>>   My Info:   Win7_64, Nightly 47, 32bit, ID 20160218030349
This is long-standing annoying bug. See screencast if my detailed STR are unclear.

STR:
1. Open attached "testcase 1"
2. Hover mouse over the string "was" in the line starting with "There's 95 bugs",
   between "a" and "s" in that string.
3. DoubleClick without releasing the left mouse button in the end, i.e.:
   In less than 0.25s:  press left mouse button, release left mouse button, press left mouse button
  [Do NOT move mouse pointer in Step 3 !!!]
4.A) Move mouse pointer to the string "was" in the line starting with "There's 94 bugs",
     between "a" and "s" in that string.
4.B) Move mouse pointer to the string "bug " in the line starting with "There's 95 bugs",
     between "u" and "g" in that string.
5. Move mouse pointer to the string "was" in the line starting with "There's 95 bugs",
   between "a" and "s" in that string.
6. Move mouse pointer to the string "fixed" in the line starting with "There's 95 bugs",
   between "x" and "e" in that string.
7. Release left mouse button pressed in Step 3.

AR:  Selected text is "fixed", i.e. the word where selection started is not selected.
ER:  Selected text should be "was fixed".

This was regressed twice.

1st regression - between 2008-10-17 and 2008-10-18 (bug 415707!)
2008-10-17 - Everything works as expected.
2008-10-18 - During Step 5 the word where selection started flickers, but stays selected.
(Actually it's possible to get that word non-selected, but there's no sense to tell the STR on that)
> http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8d0e5b53857f&tochange=fa62ea8a60ca

2nd regression - between 2011-06-30 and 2011-07-01 (regressionwindow-wanted)
2011-06-30 - During Step 5 the word where selection started flickers, but stays selected.
2011-07-01 - After Step 5 the word where selection started becomes non-selected (i.e. current result)
> http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d452aaf438f1&tochange=beceddeee3f4

Screencast:
> https://dl.dropboxusercontent.com/s/xb3z1oc6b1ioz2s/screencast%201%20-%20%27DoubleClick%20then%20drag%27%20doesn%27t%20select%20the%20word%20where%20selection%20started.webm?dl=0

Comment 1

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Hi,

I have tested this issue on latest Firefox (44.0.2) release, latest Nightly (47.0a1) build and I have managed to reproduce it. 

Firefox: 47.0a1, Build ID: 20160225030209
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Firefox: 44.0.2Build ID: 20160210153822
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0

Considering that the reporter provided the regression window I will remove the "regressionwindow-wanted" keyword. 

Thanks,
Cosmin.

Comment 2

[arni2033]

I left "regressionwindow-wanted" keyword in cases when it's unclear which bug caused regression.
But if you think that 1-day pushlog is precise enough, then OK. I won't set that keyword in future

Comment 3

[Andrew Overholt [:overholt]]

Mats, Olli suggested you may have thoughts here.

Comment 4

[Mats Palmgren (inactive)]

Someone just needs to debug this I guess.  The code that was changed in bug 415707
seems like a good place to start.  (To be clear, it's unlikely that I'll get to
this anytime soon.)

Comment 5

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Platform triage decision: This is an old regression and does not need to be tracked. 

NI Jet: Can we find an owner to fix this and related issues with the editor?

Comment 6

[Lawrence Mandel [:lmandel] (use needinfo)]

As we're now into RC builds, this is wontfix for 47.

Comment 7

[Jet Villegas (inactive)]

Clearing out my needinfo queue. We are not going to fix this regression from 2011.