Status Update
No update yet.
Comments
pa...@google.com
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]>
[Empty comment from Monorail migration]
al...@gmail.com
Bug still exists in Chrome Version 27.0.1453.90.
Android's native browser works correctly in this regard.
Tested on HP Slate 7. Android 4.1.1
Android's native browser works correctly in this regard.
Tested on HP Slate 7. Android 4.1.1
[Deleted User] <[Deleted User]>
rb...@chromium.org
For performance Chrome android has always sent touchcancel on the start of a scroll (and so you don't get touchmove events), but this has always been problematic for compatibility with other browsers where touchcancel is much rarer - see https://crbug.com/chromium/293467 .
[Deleted User] <[Deleted User]>
is...@google.com
This issue was migrated from crbug.com/chromium/150779?no_tracker_redirect=1
[Monorail mergedinto:crbug.com/chromium/293467 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description
OS Version: Android 4.1 (Jelly Bean)
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: OK
Android Native Browser 4.1.1: OK
What steps will reproduce the problem?
1. Bind Javascript "touchmove" event to DOM element (ex. body, div)
2. In touchmove event handler, console.log either log a value or log anything
3. Scroll on targeted element to fire touchmove
What is the expected result?
Console log output should log every time touchmove is fired. touchmove should be fired on every pixel of movement.
What happens instead?
Unless you add a preventDefault() to the touchmove event the event it only fired twice.
Please provide any additional information below. Attach a screenshot if
possible.