Implement the 2016Q2 Translate UI designe spec out in

ui/views/bubble/bubble_frame_view.h

Index: ui/views/bubble/bubble_frame_view.h
diff --git a/ui/views/bubble/bubble_frame_view.h b/ui/views/bubble/bubble_frame_view.h
index 6f92883c13b51247507b4d984196bac827e19c86..62d9b8636f88e4b2c7bd1b667c545b9d6e1871ac 100644
--- a/ui/views/bubble/bubble_frame_view.h
+++ b/ui/views/bubble/bubble_frame_view.h
@@ -16,6 +16,8 @@ namespace gfx {
 class FontList;
 }
 
+FORWARD_DECLARE_TEST(TranslateBubbleViewTest, CloseButtonIn2016Q2UI);
+
 namespace views {
 
 class Label;
@@ -96,6 +98,7 @@ class VIEWS_EXPORT BubbleFrameView : public NonClientFrameView,
   FRIEND_TEST_ALL_PREFIXES(BubbleFrameViewTest, GetBoundsForClientView);
   FRIEND_TEST_ALL_PREFIXES(BubbleDelegateTest, CloseReasons);
   FRIEND_TEST_ALL_PREFIXES(BubbleDialogDelegateTest, CloseMethods);
+  FRIEND_TEST_ALL_PREFIXES(::TranslateBubbleViewTest, CloseButtonIn2016Q2UI);

[msw, 2016/04/29 20:00:03]

Can you avoid this and instead fire an [Escape] key or similar in the test?

[ftang, 2016/04/29 22:37:03]

no, I cannot.

[msw, 2016/04/29 23:43:40]

Please explain why; it's unfortunate if we need to make some random Chrome
bubble's test a friend of a common UI element... I'd rather you add
GetCloseButtonForTest() to this class.

 
   // Mirrors the bubble's arrow location on the |vertical| or horizontal axis,
   // if the generated window bounds don't fit in the monitor bounds.