Boris Zbarsky [:bzbarsky] Assignee
	Description • 13 years ago

This is spun off from bug 598482 so we can land part 24 of that without all the other bits.

	Boris Zbarsky [:bzbarsky] Assignee
	Comment 2 • 13 years ago

https://hg.mozilla.org/integration/mozilla-inbound/rev/04e2d8313601

	Boris Zbarsky [:bzbarsky] Assignee
	Comment 3 • 13 years ago

This caused about a 5% Tdhtml MozAfterPaint regression.  It seems to all be concentrated in the layers1 (57% regression) and scrolling (120% regression) tests.

Are we dispatching the synthetic mousemoves sync and triggering flushes on those or something?  If so, would it make sense to not flush on synthetic mousemoves, if we can detect them here?

	Robert O'Callahan (:roc) (email my personal email if necessary)
	Comment 4 • 13 years ago

Can we dispatch synthetic mousemoves after we've flushed in the refresh driver, or something like that?

I'd actually like to dispatch mousemoves in the refresh driver too, to help reduce flushing.

	Ed Morley [:emorley]
	Comment 5 • 13 years ago

https://hg.mozilla.org/mozilla-central/rev/04e2d8313601

	Boris Zbarsky [:bzbarsky] Assignee
	Comment 6 • 13 years ago

Hmm.  That might be doable, yes.  I just pushed a patch to that effect to try; if it pans out I'll ask for review in a followup bug.