Implement findAnchor and computeRelativeOffset in ScrollAnchor.

third_party/WebKit/Source/core/layout/ScrollAnchorTest.cpp

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "core/layout/ScrollAnchor.h"
 
 #include "core/layout/LayoutTestHelper.h"
 
 namespace blink {
 
 static void enableScrollAnchoring(Settings& settings)
 {
     settings.setScrollAnchoringEnabled(true);
 }
 
 class ScrollAnchorTest : public RenderingTest {

[ojan, 2016/02/03 01:37:03]

I think this might be better as a SimTest. See
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit...
for examples. The advantage of a SimTest is that it runs something closer to
what an actual web page does instead of calling updateAllLifeCyclePhases outside
of the context of actually pumping a frame from the compositor. It makes the
tests a bit less fragile to refactors as we change how we do things like
updating the lifecycle phases.

[skobes, 2016/02/06 01:02:17]

This is made tricky by SimTest being in web instead of core.  Do you think we
should move ScrollAnchorTest into web?

     FrameSettingOverrideFunction settingOverrider() const override { return enableScrollAnchoring; }
 };
 
 TEST_F(ScrollAnchorTest, Basic)
 {
-    ScrollAnchor scrollAnchor(document().view()->layoutViewportScrollableArea());
-    scrollAnchor.clear();
-    EXPECT_EQ(nullptr, scrollAnchor.anchorObject());
+    setBodyInnerHTML(
+        "<style> body { height: 1000px } div { height: 100px } </style>"
+        "<div id='block1'>abc</div>"
+        "<div id='block2'>def</div>");
+
+    ScrollableArea* viewport = document().view()->layoutViewportScrollableArea();
+    viewport->scrollBy(DoubleSize(0, 150), UserScroll);
+    document().getElementById("block1")->setAttribute(HTMLNames::styleAttr, "height: 200px");
+    document().view()->updateAllLifecyclePhases();
+    EXPECT_EQ(250, viewport->scrollPosition().y());
 }
+
 }