On Fri, Jan 16, 2015 at 12:24 PM, PhistucK <phistuck@gmail.com> wrote: > Touch events contain much more data and granularity than mouse events. If > you disable them, perhaps the logic or memory used for obtaining and > storing that data can be suppressed and the memory usage or performance may > improve. > Our measurements do not support this - we have to get the data in chromium in the first place in order to generate the gesture events that ultimately give rise to the compatibility mouse events. BUT there is a significant cost associated with having the gresture events block on the touch event handling in blink. This is why we already implement various optimizations which skip sending touch events to the renderer process when there are no handlers, or no handlers at the relevant location. The scroll-blocks-on API <https://docs.google.com/a/chromium.org/document/d/1aOQRw76C0enLBd0mCG_-IM6bso7DxXwvqTiRWgNdTn8/edit> I'm working on extends this further to let you explicitly opt-out of this blocking without suppressing the touch events entirely (i.e. giving them the performance properties of PointerEvents in this regard). > > > ☆*PhistucK* > > On Fri, Jan 16, 2015 at 7:22 PM, Patrick H. Lauke <redux@splintered.co.uk> > wrote: > >> On 16/01/2015 16:57, PhistucK wrote: >> >>> Most websites do not explicitly need touch events, but only mouse events >>> (with the compatibility mouse events). So in the same vein, perhaps >>> document.disableTouchEvents should be added. >>> >> >> And why exactly? If your site does not register touch event handlers, >> then it makes no difference/does not need to be suppressed. >> >> >> -- >> 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 17:29:53 UTC