RESOLVED FIXED Bug 35239
pageX/Y co-ordinates of TouchEvent should be 0,0
https://bugs.webkit.org/show_bug.cgi?id=35239
Summary pageX/Y co-ordinates of TouchEvent should be 0,0
Ben Murdoch
Reported 2010-02-22 06:40:16 PST
Currently, the pageX/pageY properties of the TouchEvent object are set to the co-ordinates of a touch point identifying itself as a touch press, only if it is at the head of the platform list of touch points. They are not updated again until a new touch start is the first touch in the PlatformTouchEvent's set of touch points. This makes the TouchEvent.pageX/Y values fairly meaningless. To match observed behavior on the iPhone, they should be set to 0,0. The co-ordinates within the set of touches attached to the TouchEvent (e.g. TouchEvent.touches[0].pageX/Y) are being updated correctly. Patch and layout test update to follow.
Attachments
Proposed patch and updated tests. (11.40 KB, patch)
2010-02-22 06:53 PST, Ben Murdoch
no flags
Ben Murdoch
Comment 1 2010-02-22 06:53:01 PST
Created attachment 49214 [details] Proposed patch and updated tests.
Eric Seidel (no email)
Comment 2 2010-02-22 14:34:54 PST
Comment on attachment 49214 [details] Proposed patch and updated tests. OK. Is there a spec which covers any of this?
Ben Murdoch
Comment 3 2010-02-23 02:19:57 PST
(In reply to comment #2) > (From update of attachment 49214 [details]) > OK. Is there a spec which covers any of this? There's nothing official that I'm aware of. I've been using the Apple developer documentation at http://developer.apple.com/safari/library/documentation/AppleApplications/Reference/SafariJSRef/TouchEvent/TouchEvent.html and observations of how touch events work on the iPhone.
WebKit Commit Bot
Comment 4 2010-02-23 05:12:20 PST
Comment on attachment 49214 [details] Proposed patch and updated tests. Clearing flags on attachment: 49214 Committed r55146: <http://trac.webkit.org/changeset/55146>
WebKit Commit Bot
Comment 5 2010-02-23 05:12:25 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.