[Webkit-unassigned] [Bug 81779] [GTK] Scrolling doesn't work in WebKit2 since r110185
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Mar 30 07:46:24 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=81779
--- Comment #10 from Zan Dobersek <zandobersek at gmail.com> 2012-03-30 07:46:24 PST ---
(In reply to comment #8)
> Changes made cause the animation scheduling to be done through ChromeClient only if the port is using display refresh monitor. Gtk is currently using display refresh timer (sort of a fallback), which was not accounted for in that revision. That's causing the scrolling animations not to be scheduled and done.
>
I actually got this part wrong. Chromium doesn't use neither display refresh monitor nor the refresh timer, but pipes the request through to ChromeClient (the WebViewImpl[1]). The request is then handled in Chromium and WebViewImpl::updateAnimations[2] is called, relaying the animation serving request back to FrameView.
I wonder if it would make sense to go along a similar way, exposing some API through which user would be able to throttle animation updates to desired refresh rate, enable vsync (if applicable) etc.
[1] http://trac.webkit.org/browser/trunk/Source/WebKit/chromium/src/WebViewImpl.cpp#L3207
[2] http://trac.webkit.org/browser/trunk/Source/WebKit/chromium/src/WebViewImpl.cpp#L1368
--
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