preventDefault() for mousemove event prevents spin-button behavior
Reported by
truefus...@gmail.com,
Jan 17 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Go here: https://jsfiddle.net/v9maqc0c/ 2. Try to increment (or decrement) the visible input field using the HTML 5 controls (i.e. the up and down arrows). 3. Behold! What is the expected behavior? The value should change and mousemove event should not fire if mouse is not moving. Even if mouse moves when clicking, I don't think preventDefault() should prevent value changes for mousemove since mousemove default behavior for an input field should not relate to value changes. What went wrong? Mousemove event fires when I attempt to change the value using the HTML 5 input controls, and event.preventDefault() kicks in, preventing value changes. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 There may have been a point in time where this did work as expected, but I can't remember. I also have no idea if this affects other input types, but this current issue prevents further development on Chrome.
,
Jan 18 2017
Interesting, mousemove is not supposed to have a default action: https://w3c.github.io/uievents/#event-type-mousemove Works correctly in Firefox and Safari. Still broken in Chrome 42 so not a recent regression.
,
Jan 19 2017
Spin button uses mousemove to check the pointer position while pressing the button. I think it's possible to stop using mousemove by UA Shadow DOM structure change.
,
Aug 7 2017
Any chance this can be bumped up to a priority higher than 3? 7 months and at least 4 major version releases since the time of this report, and it is still present. Since then I have managed to randomly come across the issue without preventDefault() and even without listening for any events on the input field, but I have not been able to isolate the cause, so unfortunately I am not able to provide any code concerning that at this time. Nevertheless, I am able to testify that this issue occurs under more than one situation.
,
Aug 7
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 8
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, Jan 18 2017