- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 06 Oct 2014 17:53:02 +0100
- To: "public-touchevents@w3.org" <public-touchevents@w3.org>
On 05/10/2014 13:33, Patrick H. Lauke wrote: > Some of the things I'd have in mind are purely stylistic (e.g. adding an > explicit, but non-normative, little box-out to > http://www.w3.org/TR/touch-events/#mouse-events to spell out what the > typical event sequence following a "tap" would be, in same way we've > done for Pointer Events in the last Note for 12.2 > https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#mapping-for-devices-that-do-not-support-hover). > Others are perhaps too implementation specific, such as spelling out > that mouse events will only be fired when there's a single touch point > on the screen - as soon as there's 2 or more, no mouse events (at least > on all platforms I tested) are being generated (again, along similar > lines of the clarification given for the fact that only primary pointers > fire mouse compat events in PE > https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-primary-pointer). As Matt pointed out that this is the place to discuss this, more focussed question to the CG: how do we work on this? Do we discuss things on the list first, or is there a bugzilla instance we use, or...? P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Monday, 6 October 2014 16:53:27 UTC