Clean compositing inputs for location APIs for sticky-affected elements.

third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp

Index: third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp
diff --git a/third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp b/third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp
index 3eda3a9d35244eb7b1a9b8b71c857b8e5156560d..073847bdefa8daf8edcea3fe12e7dc63d20c3f24 100644
--- a/third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp
+++ b/third_party/WebKit/Source/core/paint/PaintLayerScrollableArea.cpp
@@ -853,6 +853,10 @@ void PaintLayerScrollableArea::UpdateAfterLayout() {
 
   DisableCompositingQueryAsserts disabler;
   PositionOverflowControls();
+
+  // Layout of a scrollable area, or any of its descendants (sticky or
+  // otherwise), invalidates the cached sticky constraints.
+  InvalidateAllStickyConstraints();

[chrishtr, 2017/04/20 17:40:34]

This looks like an independent bug. Does it deserve its own CL?

[smcgruer, 2017/04/26 14:37:07]

Yes, it probably does. Removed the scroll related stuff, will create a new CL
for it. This means that scrollIntoView/scrollIntoViewIfNeeded will still be
broken after this CL.

 }
 
 void PaintLayerScrollableArea::ClampScrollOffsetAfterOverflowChange() {