Adjust positioning of cros tray bubbles.

ash/common/system/tray/tray_constants.cc

Index: ash/common/system/tray/tray_constants.cc
diff --git a/ash/common/system/tray/tray_constants.cc b/ash/common/system/tray/tray_constants.cc
index 304d9ccdd86595d1e2f33fc09efc801b504333b3..919466da77325156dc5247488501edf10cc72761 100644
--- a/ash/common/system/tray/tray_constants.cc
+++ b/ash/common/system/tray/tray_constants.cc
@@ -104,7 +104,7 @@ const int kTrayPopupInkDropInset = 4;
 int GetTrayConstant(TrayConstant constant) {
   const int kTrayItemHeightLegacy[] = {38, kTrayItemSize, kTrayItemSize};
   const int kTraySpacing[] = {4, 0, 0};
-  const int kTrayPaddingFromEdgeOfShelf[] = {3, 4, 4};
+  const int kTrayPaddingFromEdgeOfShelf[] = {3, 3, 3};

[tdanderson, 2016/11/14 04:03:21]

With this change, can you check that the system menu is still clickable when the
mouse cursor is in the very bottom right corner of the screen (for a horizontal
or right-aligned shelf) and in the very bottom left corner of the screen (for a
left-aligned shelf)? IIRC that is the purpose of |extended_padding| in
StatusAreaWidgetDelegate::SetBorderOnChild().

[Evan Stade, 2016/11/15 01:11:55]

it's hard to check that when chromeos is running in a window (it seems to still
work but I can't be sure I'm clicking on the cornermost pixel). That said I
don't see why this would cause a problem --- it should just move the last tray
item one dp closer to the edge.

   const int kTrayPopupItemHeight[] = {46, 48, 48};
   // FixedSizedImageViews use the contained ImageView's width for 0 values.
   const int kTrayPopupItemMainImageRegionWidth[] = {0, 48, 48};