On Sun, Feb 24, 2013 at 1:41 PM, Neil <n...@parkwaycc.co.uk> wrote: > Robert O'Callahan wrote: > > I suppose we could try ignoring WM_MOUSE_MOVEs when there's a Gecko event >> pending, but that sounds kinda scary. I think deferring DOM mousemove >> events to the next refresh driver tick would be safer than that. >> >> > Currently we peek for WM_MOUSEFIRST to WM_MOUSELAST, where conveniently > WM_MOUSEFIRST == WM_MOUSEMOVE, so couldn't we exclude WM_MOUSEMOVE from the > native events that we check for? Then they would get picked up when the > system wasn't so busy.
WM_MOUSEMOVE events, like other native events, would still take priority over all Gecko events and potentially starve the refresh driver. 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
