RESOLVED FIXED 36978
Very bad scrolling-performance with the Trackpad at http://www.apple.com/ipad/app-store/
https://bugs.webkit.org/show_bug.cgi?id=36978
Summary Very bad scrolling-performance with the Trackpad at http://www.apple.com/ipad...
Mehmet
Reported 2010-04-01 13:17:20 PDT
Hello Webkit-Team, the two-finger-scrolling-performance is very bad and jerky at following site: http://www.apple.com/ipad/app-store/ Hardware: MacBook 3,1 OS: 10.6.3 Tested with: Safari 4.0.5 and Nightly Build r56912 Thanks in advance. Mehmet
Attachments
Patch (3.15 KB, patch)
2010-04-02 16:44 PDT, Simon Fraser (smfr)
darin: review+
Sam Weinig
Comment 1 2010-04-01 19:06:48 PDT
Simon Fraser (smfr)
Comment 2 2010-04-02 16:44:24 PDT
Darin Adler
Comment 3 2010-04-02 17:03:38 PDT
Comment on attachment 52466 [details] Patch > + // Check to see if the image changed; we have to do this because the call to > + // CGImageCreateCopyWithColorSpace() below can create a new image every time. > + if (m_uncorrectedContentsImage && CFEqual(m_uncorrectedContentsImage.get(), newImage)) > + return; Wow, does CFEqual actually work on CGImages!? And it compares every bit? > + m_uncorrectedContentsImage = m_pendingContentsImage = newImage; Could you do these on separate lines? It's too easy to overlook the second assignment when it's all on one line. r=me assuming you tested
Simon Fraser (smfr)
Comment 4 2010-04-02 17:26:08 PDT
(In reply to comment #3) > (From update of attachment 52466 [details]) > > + // Check to see if the image changed; we have to do this because the call to > > + // CGImageCreateCopyWithColorSpace() below can create a new image every time. > > + if (m_uncorrectedContentsImage && CFEqual(m_uncorrectedContentsImage.get(), newImage)) > > + return; > > Wow, does CFEqual actually work on CGImages!? And it compares every bit? I don't care about bit-for-bit comparisons; this just checks to see if this image is the same as the last one we set. I guess I could test for pointer equality? > > + m_uncorrectedContentsImage = m_pendingContentsImage = newImage; > > Could you do these on separate lines? It's too easy to overlook the second > assignment when it's all on one line. Will do.
Simon Fraser (smfr)
Comment 5 2010-04-02 18:05:49 PDT
Note You need to log in before you can comment on or make changes to this bug.