- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 16 Jan 2015 16:37:15 +0000
- To: public-touchevents@w3.org
On 16/01/2015 16:25, Rick Byers wrote: > I'm not sure an API on document is the best pattern though - it implies > that the decision can be made for the page as a whole, when often a page > is built out of components with different expectations/assumptions. > Maybe it should be a CSS property instead? Think this may still be dangerous (unless we define that property not to be inherited), as devs may simply set it on HTML or BODY, and then have issues where (3rd party?) components still rely/need mouse compat events. > Or maybe it should be a > preventMouseEvents() method on TouchEvent? Purely to my mind, that seems the more logical approach, as you're trying to deal with/prevent default mouse compat events...so similar to how you'd handle regular preventDefault() 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 Friday, 16 January 2015 16:37:39 UTC