Chromium Code Reviews

Unified Diff: third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h

Issue 2631853002: Give OOPIF FrameViews their own scroll animation timelines and hosts (Closed)
Patch Set: Attempt to fix tests Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Index: third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h
diff --git a/third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h b/third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h
index 7d97eb4cf52feb131f0b7b11c6b0eb2fd57f0970..c70717de3976c24021bd229f6e506f75396cd8fc 100644
--- a/third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h
+++ b/third_party/WebKit/Source/core/page/scrolling/ScrollingCoordinator.h
@@ -61,8 +61,12 @@ class CORE_EXPORT ScrollingCoordinator final
~ScrollingCoordinator();
DECLARE_TRACE();
- void layerTreeViewInitialized(WebLayerTreeView&);
- void willCloseLayerTreeView(WebLayerTreeView&);
+ // The FrameView argument is optional, nullptr causes the the scrolling
+ // animation host and timeline to be owned by the ScrollingCoordinator. When
+ // not null, the host and timeline are attached to the specified FrameView.
+ // A FrameView only needs to own them when it is the view for an OOPIF.
+ void layerTreeViewInitialized(WebLayerTreeView&, FrameView*);
+ void willCloseLayerTreeView(WebLayerTreeView&, FrameView*);
void willBeDestroyed();

Powered by Google App Engine