[Webkit-unassigned] [Bug 45560] Expose an entry point to Chrome for scrolling portions of the page

Tue Sep 14 07:41:42 PDT 2010

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

Dimitri Glazkov (Google) <dglazkov at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dglazkov at chromium.org

--- Comment #5 from Dimitri Glazkov (Google) <dglazkov at chromium.org>  2010-09-14 07:41:42 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > Why do we want the logic for initiating scrolls outside of WebKit?
> 
> Various gestures may wish to initiate scrolling.  But I wanted to put the code for recognizing gestures in Chrome (as opposed to WebKit) to make it possible for both Views-based UI code and the RenderView to share as much of the gesture detection code as possible.
> 
> Adding this new entry point seemed to provide a clearer separation of concern than crafting and delivering fake mouse wheel events from the RenderView.

Wouldn't it be a Good Thing to have this code in WebCore? It seems that sharing this code across various ports of WebKit is a more interesting idea than sharing it between parts of Chrome.

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