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.
--
Warning: May contain traces of nuts.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
