We only use the MainThreadScrollingReason "ForcedOnMainThread" if we install a page overlay (didInstallPageOverlay), which clients can do arbitrarily. We probably should still use tile-sized tiles in this case (this will also prevent us from falling into gigantic tiles for WebKit2 find-in-page, among other things).
And the web inspector.
Created attachment 182012 [details] no giant tiles
Comment on attachment 182012 [details] no giant tiles View in context: https://bugs.webkit.org/attachment.cgi?id=182012&action=review > Source/WebCore/rendering/RenderLayerBacking.cpp:204 > - if (scrollingCoordinator->shouldUpdateScrollLayerPositionOnMainThread()) > + if (scrollingCoordinator->mainThreadScrollingReasons() & ~ScrollingCoordinator::ForcedOnMainThread) I think you should explain what this does with a comment.
(In reply to comment #3) > (From update of attachment 182012 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=182012&action=review > > > Source/WebCore/rendering/RenderLayerBacking.cpp:204 > > - if (scrollingCoordinator->shouldUpdateScrollLayerPositionOnMainThread()) > > + if (scrollingCoordinator->mainThreadScrollingReasons() & ~ScrollingCoordinator::ForcedOnMainThread) > > I think you should explain what this does with a comment. okiedokie.
<rdar://problem/12959143>
http://trac.webkit.org/changeset/139258