Tile update problems in iframe after scrolling page too soon after load
authorantti@apple.com <antti@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 18 Apr 2019 16:31:58 +0000 (16:31 +0000)
committerantti@apple.com <antti@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 18 Apr 2019 16:31:58 +0000 (16:31 +0000)
commitd979bc0c5800bf6cf56b748c606085700c2226a1
tree5e9730bcf32596178cb04ee74b91a4a6f0870a39
parent7b17832a62528639e644edaa5af833496e591928
Tile update problems in iframe after scrolling page too soon after load
https://bugs.webkit.org/show_bug.cgi?id=197057
<rdar://problem/49913663>

Reviewed by Simon Fraser.

We end up destroying FrameHosting scrolling node when we shouldn't.

No test, despite attempts I couldn't get this state to stick. The problem is that in
most cases the destroying scrolling node gets immediately recreated and connected again.
Getting into testably buggy state requires some very specific layer tree configuration update.

* rendering/RenderLayerBacking.cpp:
(WebCore::RenderLayerBacking::detachFromScrollingCoordinator):

Test the right thing.

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@244426 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/rendering/RenderLayerBacking.cpp