- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 30 May 2016 19:32:26 +0100
- To: public-touchevents@w3.org
On 30/05/2016 16:42, Rick Byers wrote: > I agree. Hit-testing (finding the node at a position) is a non-trivial > operation, and for touch UIs it's often not necessary (or even > desirable) to do this on every movement. So we wouldn't want to add > this to every TouchEvent by default. We could have a method like > "Touch.getNodeUnderTouch()" to let developers opt into it when they > actually need it, but this would just be implemented with > elementFromPoint so adding it to the Touch API probably doesn't buy you > anything. I agree as well that an explicit API seems overkill here, as internally the browser is likely to incur the same hit testing overhead as an explicit elementFromPoint() call. 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, 30 May 2016 18:32:51 UTC