Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3725)

Unified Diff: cc/trees/property_tree.h

Issue 2733633002: Handle nested position:sticky elements correctly (compositor) (Closed)
Patch Set: Revert float changes to unittests too Created 3 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: cc/trees/property_tree.h
diff --git a/cc/trees/property_tree.h b/cc/trees/property_tree.h
index 412e653e858e88e9b568296bb70e0b662fa67bd2..65d824782992523f4f79e69e2e34736b34523b34 100644
--- a/cc/trees/property_tree.h
+++ b/cc/trees/property_tree.h
@@ -128,17 +128,7 @@ class CC_EXPORT PropertyTree {
PropertyTrees* property_trees_;
};
-struct StickyPositionNodeData {
- int scroll_ancestor;
- LayerStickyPositionConstraint constraints;
-
- // This is the offset that blink has already applied to counteract the main
- // thread scroll offset of the scroll ancestor. We need to account for this
- // by computing the additional offset necessary to keep the element stuck.
- gfx::Vector2dF main_thread_offset;
-
- StickyPositionNodeData() : scroll_ancestor(-1) {}
-};
+struct StickyPositionNodeData;
class CC_EXPORT TransformTree final : public PropertyTree<TransformNode> {
public:
@@ -301,6 +291,35 @@ class CC_EXPORT TransformTree final : public PropertyTree<TransformNode> {
std::vector<StickyPositionNodeData> sticky_position_data_;
};
+struct StickyPositionNodeData {
+ int scroll_ancestor;
+ LayerStickyPositionConstraint constraints;
+
+ // This is the offset that blink has already applied to counteract the main
+ // thread scroll offset of the scroll ancestor. We need to account for this
+ // by computing the additional offset necessary to keep the element stuck.
+ gfx::Vector2dF main_thread_offset;
+
+ // In order to properly compute the sticky offset, we need to know if we have
+ // any sticky ancestors both between ourselves and our containing block and
+ // between our containing block and the viewport. These ancestors are then
+ // used to correct the constraining rect locations.
+ int nearest_node_shifting_sticky_box;
+ int nearest_node_shifting_containing_block;
+
+ // For performance we cache our accumulated sticky offset to allow descendant
+ // sticky elements to offset their constraint rects. Because we can either
+ // affect the sticky box constraint rect or the containing block constraint
+ // rect, we need to accumulate both.
+ gfx::Vector2dF total_sticky_box_sticky_offset;
+ gfx::Vector2dF total_containing_block_sticky_offset;
+
+ StickyPositionNodeData()
+ : scroll_ancestor(TransformTree::kInvalidNodeId),
+ nearest_node_shifting_sticky_box(TransformTree::kInvalidNodeId),
+ nearest_node_shifting_containing_block(TransformTree::kInvalidNodeId) {}
+};
+
class CC_EXPORT ClipTree final : public PropertyTree<ClipNode> {
public:
bool operator==(const ClipTree& other) const;

Powered by Google App Engine
This is Rietveld 408576698