some updates

for the first mousedown, the extra mousemove happens after just mousedown

start from the second mousedown, the extra mousemove won't happen after mousedown, but still happen after mouseup

tested multiple widows PC, win 7 win 8, as well as 52.0.2717.0 canary (64-bit) on windows 10.  this bug always happen. click event is always followed by a extra mousemove.  
and the first time when browser is opened this can happen just after mousedown

we can't reproduce this in osX

I don't understand why this is Pri-3.

this is a bad regression. any js logic that relys on movemove event could get broken.

Yes sorry I didn't see it was a regression; it was originally marked as a bug not a regression.

Yes, this is a regression. The mousemove right after mousedown doesn't occur in Chrome 50.0.2661.75 (tested in Win 7).

Looks like the bug do repro in Chrome 50.0.2661.75 in Win 7, and this happens right after the window loses focus. Comment #6 was testing with new tab, not a new window. Navid confirms that we don't even need to close the window, just clicking on desktop causes this the next time.

z.zhou@ since you said it was working before, do you have a working version of Chrome for this? I don't seem to be able to find a version that we don't send mousemove after a down in your scenario.

there are 2 issues here:
1) extra mousemove after mousedown , only when first time you start chrome
I can't reproduce this in old version, just tested chromium 48, it works correctly : https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/358636/

2) extra mousemove after click, I can still reproduce this in old version.



right now 1) is a bigger issue for us, because we have custom drag drop logic in js.  a mousemove after a mouse down will be treated as a drag.

2) is ok for now, I guess an extra mousemove when mouse is not down won't  cause any issue in most websites.

The second issue will be addressed in  Issue 161464 .
I'll look into the fist issue which seems to be a regression.

I was going to look at what I thought the extra mousemove. But even in the revision that you gave it is happening. 
What I saw as the sequence of the events when the browser is out of focus and the first click is in the blue button is:

...
click 0
mouseup 0
mousemove 0
mousedown 0
...


Are you referring to this mousemove? So this still does exist even in Win/358636.

I see,  seems it's another issue, the original issue is not about lose focus.

my issue was, when you open chrome for the first time,  the browser does get focus, and I enter url there, then mousedown.

that's the issue that happens in new version, not old version.

The above issue is reproducible on Windows 10 with chrome versions : 50.2661.87(Stable), 51.0.2704.22(Beta) & 52.0.2718.0(Canary).

The above mentioned behavior can be seen from M30 build - 30.0.1549.0. Extra mousemove is seen when clicked in red/green area.

I removing the bisect label for now. Feel free to add if required. 


Note: 
1. Issue seen only on Windows OS.
2. This behavior not seen on FF 45 and IE edge.
3. Attach is the screencast.


Thank you!

Deleted: 607019.mp4 2.3 MB

607019.mp4 2.3 MB Download

This is not a regression then.

@ashejole what you tested in your video is the mousemove after the click/mouseup which is this  Issue 161464 .
What rinick@gmail.com is reporting here is a mousemove after the mousedown which was not in your video.

rinick@ I don't seem to be able to reproduce the mousemove after mousedown the way you are suggesting by opening a new tab and pasting the url and clicking on the div. That would be great if you can create a video like what @ashejole created to show the problem.

@nzolghadr open new tab won't reproduce it, you will have to close chrome application and restart it. it only happens on the first mousedown event
also it only happens in windows

still can reproduce this against Chrome Canary 61.0.3114.0

i am ensure that proplem (extra mousemove after mousedown) appear in some windows machine. 

I'm confused that this bug has not been solved after such half a year ?

my chrome version is 59.0.3071.86

I've been looking into this issue today and have been experiencing it regularly with Chrome 60.0.3112.90 on Windows 7. If I relaunch the browser and immediately visit the example, things will often function normally at first:

click 0
mouseup 0
mousedown 0

However, once I open a second tab and do some browsing, this page will start adding mousemove events immediately after mousedown:

click 0
mouseup 0
mousemove 0
mousedown 0

Oddly enough, my most recent attempt caused mousemove to be called once every second while holding mousedown!

On a side note, Browserstack tests were not able to replicate the issue.