[Webkit-unassigned] [Bug 17052] Scrolling with arrow keys does not update cursor

[bugzilla-daemon at webkit.org]

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





--- Comment #23 from Darin Adler <darin at apple.com>  2009-07-16 10:33:56 PDT ---
I thought further about the best way to address this issue.

It seems to me that scrolling and elements moving is made real when we do
layout, so we may want to hook tis detection into the layout timer and layout
machinery. After layout we can check if the current mouse position is still
over the same thing it was over before, and if not send the appropriate events.

We'll have to check that layout covers all the scrolling cases. If not, then we
can have a separate set of the same kind of code for scrolling.

Moving windows is yet another similar case.

In all cases, it seems having a record of where we previously reported the
mouse over is helpful so we can see if the new location is different in any
way. I'm thinking that we might want to keep the actual DOM event that was sent
to see if it's at all different.

Besides the DOM events, we're also interested in making sure the cursor has the
correct shape in these various cases.

One simple model for this might be to have a recheckMousePositionSoon function
on EventHandler that could be called in all places where there was a change
that might require re-communicating the mouse position to the web page.

I don't think that a check on the way in and the way back out of event handlers
is the right bottleneck for this. I think it's the actual changes to rendering,
scrolling, and window position that are apropros.

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