Last Comment Bug 855779 - document.createTouch does not match the specification; requires explicit clientX/clientY
: document.createTouch does not match the specification; requires explicit clie...
Status: NEW
: compat
Product: Core
Classification: Components
Component: DOM: Events (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
http://w3c-test.org/webevents/tests/t...
: 815420 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-28 11:22 PDT by Matt Brubeck (:mbrubeck)
Modified: 2014-03-14 21:52 PDT (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Matt Brubeck (:mbrubeck) 2013-03-28 11:22:09 PDT
Gecko's implementation of document.createTouch is not compatible with the Touch Events v1 spec, or the behavior of other browser.

This causes a failure in the createTouch test at:
http://w3c-test.org/webevents/tests/touch-events-v1/submissions/Nokia/create-touch-touchlist.html
Comment 1 Boris Zbarsky [:bz] 2013-03-28 11:25:44 PDT
Details?  Which part of the test do we fail, and how does our behavior differ from other UAs?
Comment 2 Matt Brubeck (:mbrubeck) 2013-03-28 11:39:21 PDT
Gecko expects separate clientX and clientY arguments to createTouch.  These arguments are not present in other browsers.  Other browsers set the clientX and clientY properties based on the pageX and pageY arguments.

The test failure is:

"assert_equals: touch.clientX is touch.pageX - window.pageXOffset. expected 15 but got 0"
Comment 3 Boris Zbarsky [:bz] 2013-03-28 11:52:53 PDT
Ah, I see.  So just a matter of ripping out the client* from the _middle_ of the signature (and hoping no one is using it, fun) and computing them on the back end, ok....

The spec does not define how the clientX and clientY are computed.  It probably needs to do that, if it's testing something about it.
Comment 4 Wesley Johnston (:wesj) 2013-03-28 12:26:23 PDT
*** Bug 815420 has been marked as a duplicate of this bug. ***
Comment 5 Olli Pettay [:smaug] 2013-03-28 14:15:25 PDT
When this stuff was implemented, we followed the spec.

Note You need to log in before you can comment on or make changes to this bug.