- From: Rick Byers <notifications@github.com>
- Date: Tue, 27 Oct 2015 12:40:08 -0700
- To: w3c/touch-events <touch-events@noreply.github.com>
Received on Tuesday, 27 October 2015 19:40:42 UTC
This looks fine to me, thanks! For the record, I'm not aware of any implementation that actually fires touchcancel when touches move to an area controlled by a plugin (due to implicit capture where you move after touchstart doesn't really matter). The main use case I'm aware of in practice for touchcancel is when the browser state changes such that it no longer has access to input events - eg. tab/window switch, home button pressed, some modal dialog / UI element is displayed. Not sure if we want to try to describe any of these possible scenarios here. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/touch-events/pull/36#issuecomment-151620550
Received on Tuesday, 27 October 2015 19:40:42 UTC