[Webkit-unassigned] [Bug 109712] [Chromium] Compositor is applying scroll offset using 'programmatic' API

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 19 08:36:30 PST 2013


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





--- Comment #3 from John Knottenbelt <jknotten at chromium.org>  2013-02-19 08:38:52 PST ---
So my understanding is as follows:

The FrameView::setScrollPosition API, is considered to be a programmatic scroll. The programmatic scroll flag stops the 'wasScrolledByUser' flag from being set. 

The wasScrolledByUser flag controls whether the scroll position should be restored when the page loads. If the user has already scrolled the page, the scroll position should not be restored.

wasScrolledByUser can be set from EventHandler::setFrameWasScrolledByUser() in response to certain scroll events, for example EventHandler::scrollOverflow.

The question, then, is: should scroll updates from Chromium's compositor be considered to be programmatic scrolls or user scrolls?

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


More information about the webkit-unassigned mailing list