On Mon, Feb 18, 2013 at 4:51 PM, Robert O'Callahan <rob...@ocallahan.org> wrote: > On Tue, Feb 19, 2013 at 1:40 PM, Brian Birtles <bbirt...@mozilla.com> wrote: > >> I'm not sure if this is a relevant data point but we had an issue[1] with >> touch event coalescing on fennec that produced poor results for the >> following drawing application on some devices such as the Dell Streak: >> >> >> http://parapara-editor.**mozlabs.jp/test<http://parapara-editor.mozlabs.jp/test> >> >> This application uses splines to interpolate between the points but still >> the lack of events produced poor results. It was fixed by turning off touch >> event coalescing. See bug 757680. >> > > Thanks, that's helpful.
For drawing programs it does indeed seem true that the more mousemove events that we dispatch, the better the user experience will be. But I would expect that in the majority of other cases, each mousemove event will not leave persisted data and dispatching more mouse moves will simply mean that the page will redo the same calculations over and over only. The result is that at best 60 results per second being used to affect what's drawn on screen. One possible solution is to allow pages to opt in to high-precision mousemove events. Then a drawing program could do that on the mousedown event end opt out again on mouseup. Or if it's really lazy opt in for the lifetime of the page. Something like this would have to be coordinated with other vendors of course. Given that it looks like Chrome is throtteling to 60 mousemove events per second, I would expect them to be interested in working on such an API. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
