- From: Matt Brubeck <mbrubeck@mozilla.com>
- Date: Tue, 25 Jan 2011 07:20:38 -0800
- To: Doug Schepers <schepers@w3.org>
- CC: "public-webevents@w3.org" <public-webevents@w3.org>, Arthur Barstow <art.barstow@nokia.com>
On 01/25/2011 06:41 AM, Doug Schepers wrote: > Rather later than promised, but here is a first draft of the Touch > Interface spec: > http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html After a first glance at the spec, here are some questions for discussion: * On which element(s) are these touch events dispatched, especially in the case of simultaneous touches on different elements? * Do elements "capture" touch events, as they do in current WebKit browsers? * What are the advantages and disadvantages of the TouchList model, compared to the one-event-per-touch model in Gecko? (See the Landscape wiki for some background and previous discussion.) * The "touchcancel" event is very narrowly defined here. Should we leave implementers more discretion to cancel events for other reasons? (For example, if the browser window becomes hidden mid-touch, or if the hardware detects that the touch slides past the edge of the screen.)
Received on Tuesday, 25 January 2011 15:22:04 UTC