Position autofill popup widgets correctly under --site-per-process

components/autofill/core/browser/test_autofill_driver.cc

 // Copyright 2013 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 "components/autofill/core/browser/test_autofill_driver.h"
 
 #include "base/test/sequenced_worker_pool_owner.h"
 #include "base/threading/sequenced_worker_pool.h"
+#include "ui/gfx/geometry/rect_f.h"
 
 namespace autofill {
 
 TestAutofillDriver::TestAutofillDriver()
     : blocking_pool_owner_(
           new base::SequencedWorkerPoolOwner(4, "TestAutofillDriver")),
       url_request_context_(NULL) {}
 
 TestAutofillDriver::~TestAutofillDriver() {}
 
@@ skipping 45 matching lines @@
     const base::string16& value) {
 }
 
 void TestAutofillDriver::RendererShouldPreviewFieldWithValue(
     const base::string16& value) {
 }
 
 void TestAutofillDriver::PopupHidden() {
 }
 
+gfx::RectF TestAutofillDriver::TransformBoundingBox(

[Charlie Reis, 2016/01/21 00:33:03]

Is there any way to test the new API, either here or in content/?

[kenrb, 2016/01/22 18:33:58]

The API is tested implicitly by SitePerProcessBrowserTest.CreateContextMenuTest,
which uses the TransformPointToRootCoordSpace in the same way as we use it here.
Context menus are easier to test this with because the browser can provide the
coordinates of the mouse click that generates the context menu (and then verify
that they have been converted back to the original coords), whereas for popups
the coordinates come from the page content and I have had trouble finding a way
to know what the correct values are.

[Charlie Reis, 2016/01/22 23:04:54]

Acknowledged.

+    const gfx::RectF& bounding_box) {
+  return bounding_box;
+}
+
 }  // namespace autofill