Re: WebEvents-ISSUE-14: Specify createTouch and createTouchList

I pushed a proposal for a new interface (DocumentTouch) to be 
implemented by the Document element, containing createTouch and 
createTouchList methods:

http://dvcs.w3.org/hg/webevents/rev/e8bb9dc16d4e
http://dvcs.w3.org/hg/webevents/rev/299f0072d6de

I have one open question I'd like to raise:  In WebKit, createTouch 
takes pageX/pageY as arguments and computes clientX/clientY.  This is 
inconsistent with other DOM methods like initMouseEvent, which takes 
clientX/clientY as arguments and computes pageX/pageY.

The spec now includes both pairs as parameters, but makes client* 
optional.  Thus it is compatible with content that uses the WebKit 
interface, and with Gecko nightly builds (which include both pairs of 
parameters).  Should we keep the spec as it is, or should we drop one 
pair or the other?

Received on Thursday, 28 April 2011 18:09:41 UTC