Bug 248119

Summary: pointerevent movementX and movementY are both undefined only in iOS Safari
Product: WebKit Reporter: Joe Pea <joe>
Component: UI EventsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ahmad.saleem792, akeerthi, a_protyasha, argyle, joe, karlcow, richard_robinson2, rniwa, simon.fraser, webkit-bug-importer, wenson_hsieh
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari 16   
Hardware: iPhone / iPad   
OS: iOS 16   
See Also: https://bugs.webkit.org/show_bug.cgi?id=258780
Attachments:
Description Flags
picture proof of issue none

Joe Pea
Reported 2022-11-18 20:19:16 PST
This code logs undefined only in iOS Safari (iPhone/iPad): document.documentElement.addEventListener( 'pointermove', e => console.log( 'movement', e.movementX, e.movementY ) ) It works fine in every other browser, even in macOS desktop Safari, and Chrome, Firefox, Edge in all OSes (except in iOS because they use WebKit there).
Attachments
picture proof of issue (1.04 MB, image/png)
2023-04-19 12:15 PDT, Adam Argyle
no flags
Radar WebKit Bug Importer
Comment 1 2022-11-18 22:41:26 PST
Karl Dubost
Comment 2 2022-11-20 21:34:18 PST
Probably a duplicate of Bug 246067 *** This bug has been marked as a duplicate of bug 246067 ***
Adam Argyle
Comment 3 2023-04-19 12:15:33 PDT
Created attachment 465985 [details] picture proof of issue Tested on iOS 16 and iOS 16.4 Safari and this bug still exists and should not be marked fixed. Screenshot shows iOS 16.4 inspected by Safari and the value for e.movementX is undefined.
Ryosuke Niwa
Comment 4 2023-04-19 15:07:12 PDT
(In reply to Adam Argyle from comment #3) > Created attachment 465985 [details] > picture proof of issue > > Tested on iOS 16 and iOS 16.4 Safari and this bug still exists and should > not be marked fixed. Screenshot shows iOS 16.4 inspected by Safari and the > value for e.movementX is undefined. On which event are you seeing this?
Adam Argyle
Comment 5 2023-04-20 08:04:01 PDT
pointermove 👍🏻
Joe Pea
Comment 6 2023-08-08 17:49:47 PDT
This is still happening on my iPhone 13 with iOS 16.6.
Note You need to log in before you can comment on or make changes to this bug.