[Webkit-unassigned] [Bug 99940] Should only fire a single set of mouse events and update hover state once when scrolling is done

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=99940


James Robinson <jamesr at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |davemoore at google.com




--- Comment #5 from James Robinson <jamesr at chromium.org>  2012-10-22 20:32:06 PST ---
(In reply to comment #4)
> James/Nat, listening to mouse events currently disables threaded scrolling, right?

Listening to mousewheel events prevents handling mousewheels as scrolls off of the main thread.  I don't think that's what this bug is about, though.

> Thinking about this more, I kind of like the idea of not firing them at all until the scroll is done. That appears to be what Gecko does, although I haven't looked at their source to confirm. What I like about this approach is that it would mean that mouse event handlers wouldn't need to disable threaded scrolling.

I don't think this will have any impact one way or the other on threaded scrolling.  The only thing that's relevant for threaded scrolling are input events with a default action of scrolling that can be cancelled.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.