- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 05 Mar 2016 11:07:21 +0000
- To: public-pointer-events@w3.org
unless i'm misunderstanding, i'd say that it's important that pointer events are consistent in the sequence of events they dispatch, but that it would require quite a bit of extra work to somehow define that the compat mouse events also need to have a self contained mapping. fundamentally, you're trying to shoehorn the concept of mouse (a single pointer device) into a multi-pointer environment. it can certainly be done, but basically you want for every pointer to always "close out" the compat mouse event stream from the idealised single pointer and then "enter" the context of where the pointer just acted. a lot of effort/keeping track i'd say. my view would be: if a developer is only looking at mouse events in a multi-touch/multi-input environment, events which are there primarily for compatibility, then...they can expect some rough sequence jumps. -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/35#issuecomment-192623102 using your GitHub account
Received on Saturday, 5 March 2016 11:07:23 UTC