Robert O'Callahan writes: > On Tue, Feb 19, 2013 at 11:47 AM, Karl Tomlinson <mozn...@karlt.net> wrote: > >> Robert O'Callahan writes: >> >> > How about this idea: after processing a WM_MOUSEMOVE event, go into an >> > "anti-flood" state where WM_MOUSEMOVE is ignored. After we service the >> > Gecko event queue, exit the anti-flood state.
>> I expect "ignored" will have to be "ignored at least until there >> is another user input event" so that the document will know where >> the mouse is when a key is pressed. >> > > Why? We currently don't do anything to ensure mousemoves are flushed before > key events. When the GTK-port widget code coalesces mousemoves, it uses the coordinates of the last mousemove on the queue. There is no other suppression of mousemoves that I am aware of. I don't know exactly what happens with WM_MOUSEMOVE, it would seem unfortunate if a WM_MOUSEMOVE with an updated mouse position is not received before key events. Changing the order of events changes the meaning considerably. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
