W3C home > Mailing lists > Public > public-webevents@w3.org > April to June 2011

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

From: Arthur Barstow <art.barstow@nokia.com>
Date: Thu, 05 May 2011 08:54:13 -0400
Message-ID: <4DC29DF5.4080602@nokia.com>
To: ext Matt Brubeck <mbrubeck@mozilla.com>, Web Events Working Group WG <public-webevents@w3.org>
All - Matt checked in his proposal one week ago. If there are no 
objections to this proposal before the May 10, I will move this issue to 

On Apr/28/2011 2:09 PM, ext Matt Brubeck wrote:
> 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, 5 May 2011 12:54:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:09:33 UTC