We currently use async scrolling only when the hardware acceleration policy is set for always, but not when entering accelerating compositing mode in ondemand policy.
Created attachment 427996 [details] Patch
Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See https://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API
Comment on attachment 427996 [details] Patch Honestly speaking I prefer the approach doing that in WebPage without platfrom #if (attachment#420247 [details]) rather than in DrawingAreaCoordinatedGraphics with #if PLATFORM(GTK). But, I don't have time to Bug 225512 now. And, I admit it's a good idea not changing Cocoa-port code for this.
*** Bug 221067 has been marked as a duplicate of this bug. ***
(In reply to Fujii Hironori from comment #3) > Comment on attachment 427996 [details] > Patch > > Honestly speaking I prefer the approach doing that in WebPage without > platfrom #if (attachment#420247 [details]) rather than in > DrawingAreaCoordinatedGraphics with #if PLATFORM(GTK). > But, I don't have time to Bug 225512 now. And, I admit it's a good idea not > changing Cocoa-port code for this. Problem is that enter/exit in WebPage doesn't seem to be balanced, enter can be called more than once, and I've seen also exit/enter calls that don't really exit and enter the AC mode. That doesn't happen with the enter/exit calls in DrawingArea.
Committed r277258 (237527@main): <https://commits.webkit.org/237527@main>
Re-opened since this is blocked by bug 225740
This is not so easy in the end. with the patch we are now causing that pages enter in Ac mode when there's an iframe, for example, because async frame scrolling is enabled. I need to investigate this further.
Chris and me are working in checking some regressions since I activated the async mode in WPE testing by default (bug 224596), the problem can be related. Can you send more information of the failures you are seeing?
See https://bugs.webkit.org/show_bug.cgi?id=225644. But the test failure is not the only issue I've noticed, as I said before.