Issue metadata
Sign in to add a comment
|
mousemove reporting incorrect event button when mouse button held down
Reported by
benblac...@gmail.com,
Jun 13 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3128.0 Safari/537.36 Steps to reproduce the problem: 1. Open up example.html which adds event listeners for mousedown mousemove and contextmenu. Press and hold left mouse button down and drag. Press and hold right mouse button down and drag. 2. In current version of chrome (59.0.3071.86), holding down right and dragging results in button number 2. 3. In canary version of chrome, holding down right and dragging results in button number 0. What is the expected behavior? What went wrong? Mousemove event not reporting the correct button being held down. Did this work before? Yes 59.0.3071.86 Chrome version: 61.0.3128.0 Channel: canary OS Version: OS X 10.12.5 Flash Version:
,
Jun 13 2017
Able to reproduce the issue on the latest canary(61.0.3129.0) and the latest beta(60.0.3112.24) on Mac OS 10.12.5.
,
Jun 13 2017
This was done to fix issue 650704 and to match the spec and other vendors. Is this breaking a specific site? Did this function in the other vendors browsers before?
,
Jun 13 2017
It is breaking the chrome extension linkclump: https://github.com/benblack86/linkclump/issues/69 Specifically this line: https://github.com/benblack86/linkclump/blob/master/src/linkclump.js#L145 I can probably just delete the line since I can't remember why this logic is needed.
,
Jun 13 2017
Ya it looks to me that you should be able to just assign mouse_button in the mousedown... not sure why you do it in the mousemove.
,
Jun 14 2017
I've updated the code, so I suppose this can be closed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 13 2017