Renames WindowManagerConfig to FrameDecorationValues and moves to Display

components/mus/public/interfaces/window_manager_constants.mojom

 // 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.
 
 module mus.mojom;
 
 import "ui/mojo/geometry/geometry.mojom";
 
 enum WindowManagerErrorCode {
   SUCCESS,
@@ skipping 13 matching lines @@
   VALUE_90,
   VALUE_180,
   VALUE_270,
 };
 
 const int32 kResizeBehaviorNone = 0;
 const int32 kResizeBehaviorCanResize = 1;
 const int32 kResizeBehaviorCanMaximize = 2;
 const int32 kResizeBehaviorCanMinimize = 4;
 
+struct FrameDecorationValues {
+  mojo.Insets normal_client_area_insets;
+  mojo.Insets maximized_client_area_insets;
+  // Max width needed to display the buttons on the title bar. The buttons are
+  // aligned to the trailing edge of the titlebar.
+  // TODO(sky): this API is very narrow, and assumes a particular config.
+  uint32 max_title_bar_button_width;
+};
+
 enum TouchSupport {
   UNKNOWN,
   AVAILABLE,
   UNAVAILABLE,
 };
 
-// TODO(sky): move this to display.mojom
 struct Display {
   int64 id;
   mojo.Rect bounds;
   mojo.Rect work_area;
   float device_pixel_ratio;
   Rotation rotation;
   TouchSupport touch_support;
   bool is_primary;
+  FrameDecorationValues frame_decoration_values;

[Ben Goodger (Google), 2016/01/26 19:18:03]

It does strike me as a little odd that this very UI/WM-specific detail is
sitting here on the lower level support struct for a display. But right now it's
probably weirder to have it floating around by itself, so I guess I'm OK with
it...

 };
 
 enum WindowType {
   // These constants come from Widget::InitParams. See it for details.
   // TODO: see if we can reduce this set. For example, why do we need both
   // BUBBLE and POPUP.
   WINDOW,
   PANEL,
   WINDOW_FRAMELESS,
   CONTROL,
   POPUP,
   MENU,
   TOOLTIP,
   BUBBLE,
   DRAG,
 };