Created attachment 288031 [details] Proposed Patch to fix scrolling on twitter and other similar sites Without this patch if you go to twitter.com and try to scroll, it is very very unresponsive. To reproduce the results: Use chromium developer release to visit the page twitter.com Expected results: Normal scrolling. Actual Results: Scrolling is intermittent causing the page to be unusable in chromium. To Fix: Patch the RenderLayer.cpp inside chromium's webkit source code.
Where did this patch come from? If you wrote it, has it been submitted upstream?
Confirmed slow scrolling on twitter.
(In reply to comment #1) > Where did this patch come from? If you wrote it, has it been submitted > upstream? https://bugs.webkit.org/show_bug.cgi?id=68733 I corrected the path in the patch to work with chromium's webcore, other than that it is the same patch as on the original webkit bugzilla listing.. I haven't put anything upstream because I don't have that kind of access. However I can confirm that the patch fixes the scrolling issue with twitter in chromium-16.0.891.0 from portage, I haven't applied he patch to the 9999 version yet, but I'm sure it will also fix it there as well.
Pawel, thoughts on applying this to the dev channel (16.x)?
(In reply to comment #4) > Pawel, thoughts on applying this to the dev channel (16.x)? Please get this upstream (I think it's webkit.org in this case). I think we're *never* going to do patches like this at the distro level (maybe except for backporting), except for maybe security reasons. And hey, this is dev channel, things can be broken. There is plenty of time to get the fix upstream. I can help off-bugzilla.
Heh, there is already WebKit bug linked to this. Upstream should do its job then.
(In reply to comment #6) > Heh, there is already WebKit bug linked to this. Upstream should do its job > then. Yea, I don't understand what their hold up is on the matter either. They seem to push all important things to the back burner, and continue on working on their desired features.. The patch is a rather easy one to be fixed, there isn't any reason that Chromium devs should have let this gone unfixed for over a week especially when there is a work around for it and Webkit has confirmed the bug its self. Google sometimes amazes me at how they work on things. Without a doubt this should have been fixed over a week ago by Google devs.. Instead they just say "We are working on it".. Come on google!
