[Webkit-unassigned] [Bug 15070] New: [gtk] ScrollView performance and possible performance improvements

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 24 08:57:28 PDT 2007


http://bugs.webkit.org/show_bug.cgi?id=15070

           Summary: [gtk] ScrollView performance and possible performance
                    improvements
           Product: WebKit
           Version: 522+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: freyther at handhelds.org


In order to implement multiple frame support the windows design was adopted.
For the non static background we currently draw too much and too often.

On each scroll we are likely to redraw the whole viewport. ScrollView calls
into the ChromeClient to update the backingstore and scroll the backing store
which in the Gtk case are currently no-op's.
To change that the expose handler of WebKitGtkPage should just paint the
backing store, ChromeClient should hold the backing store and to accelerate
scrolling we should make sure to reuse as much as possible, and finally
ScrollView should not invalidate the whole GdkWindow of the containingWindow()
when the page is scrolled. To get/see/learn more details one should take a look
at the windows port.

The interesting part is to decide how, where and what to buffer. E.g. disable
double buffering on the GdkWindow, keeping a cairo surface in ChromeClient...

Another interesting observation is ScrollView::updateScrollbars which is
creating and destroying PlatformScrollbars frequently on resizes.


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



More information about the webkit-unassigned mailing list