In Chrome 69, after it incorrectly changes to a file drag-and-drop operation, if you release the mouse button while the cursor is on top of the same image, it *then* goes into panning mode while you have no mouse button depressed and it takes a mouse click to get out of that mode.

Thanks for reporting this issue. Can you please take a video how it use to work and whats wrong now? We will try to reproduce it from our side. 

Thanks!

Recorded a video showing what Chrome 69 does.. I click and hold the mouse button down while dragging and, instead of panning the image around, you get the drag-and-drop mouse cursor with the little document icon to the upper-right of it.

Chrome 68 and all other browsers pan the image around when you hold the mouse button down and drag. You also see that when I let go of the mouse button and simply move the mouse around, *then* the image pans. It is only supposed to pan if you have the button pressed while moving the mouse.

Programmer hat on: 
- You mouse down and begin to drag, and these first few events are sent to the content and it begins to pan a tiny bit
- File drag-and-drop kicks in and now the mouse events are diverted into the drag-and-drop code and are *not* sent to the application
- When file drag-and-drop is canceled after releasing the mouse button, that event is also swallowed and not passed to the application, leaving it in a state where it still thinks the mouse button is depressed, causing mouse movement to pan the image around as if you we still holding the button down.
- Simply clicking and releasing the mouse button resets the application state and it stops panning

Deleted: issue883608.mov 9.5 MB

	issue883608.mov 9.5 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

andrew.m.paprocki@ Thanks for the update.

Able to reproduce this issue on Windows 10, Mac OS 10.13.3 and Ubuntu 17.10 on the reported version 69.0.3497.81 and latest Beta 70.0.3538.16.
Issue seems to be fixed on the latest Canary 71.0.3552.2.

Revert Bisect Information:
==========================
Good Build: 71.0.3545.0
Bad Build : 71.0.3544.0 

By running per-revision bisect script, RunTimeError was coming up. Hence by running Chromium bisect below is the Changelog URL.

https://chromium.googlesource.com/chromium/src/+log/e2a125c42c0dcc6132c138a160fb2dd0cc2badbe..be9e708ab189d52a1a673ff1819100dfe959cd54

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1210124

nzolghadr@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding 'ReleaseBlock-Stable' for M-69 as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks

That is indeed caused by my change. But that is change intentional. It is temporary reverted for now but it is coming back. Authors of the website relying on un-specified behaivor in Chrome (i.e. preventing default mousemove to prevent drag). They should listen to dragstart and prevent default that instead.
Removing stable block as it is not that critical of an issue.

Reporter, are you the developer of that website or a user?

I'm a user that spends a lot of time on that site. The site lists that the firm responsible for building the site is CINECA: https://www.cineca.it/en/content/contact

One more request. Can you try it with Chrome Canary and see whether it is resolved or not as we have reverted the change there.

The original change is reverted already and it is fixed now.