On Tue, Feb 19, 2013 at 7:24 PM, Jonas Sicking <jo...@sicking.cc> wrote:
> 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. > I think my idea for an anti-flood state makes this unnecessary. Rob -- Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28] _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
