Move convertViewportToWindow and convertWindowToViewport from

third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp

Index: third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp
diff --git a/third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp b/third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp
index b69bf78748a0bc62f544bc00393323ff0a2b6cdc..7bc953c82232237f2007c826ea63e7ff76d54539 100644
--- a/third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp
+++ b/third_party/WebKit/Source/core/inspector/InspectorHighlight.cpp
@@ -242,7 +242,7 @@ InspectorHighlight::InspectorHighlight(Node* node, const InspectorHighlightConfi
 {
     FrameView* frameView = node->document().view();
     if (frameView)
-        m_scale = 1.f / frameView->getHostWindow()->windowToViewportScalar(1.f);
+        m_scale = 1.f / frameView->getHostWindow()->windowToViewportScalar(1.f, frameView);

[dcheng, 2016/09/08 05:25:47]

This might be a dumb question, but why isn't this just plumbed through
ChromeClient itself anyway? It feels kind of random when we need to pass a
LocalFrame and when we need to pass a Widget.

(Not necessary to fix in this CL, but it doesn't seem great)

[lfg, 2016/09/08 21:40:43]

This is also used in Source/platform/scroll/Scrollbar.cpp, so it can't be
plumbed through ChromeClient with a LocalFrame -- unless we have 2 ways of
plumbing this data, which seems worse.

     appendPathsForShapeOutside(node, highlightConfig);
     appendNodeHighlight(node, highlightConfig);
     if (appendElementInfo && node->isElementNode())