[MacViews] Implement size constraints for app windows.

chrome/browser/ui/views/apps/native_frame_view_mac.h

Index: chrome/browser/ui/views/apps/native_frame_view_mac.h
diff --git a/chrome/browser/ui/views/apps/native_frame_view_mac.h b/chrome/browser/ui/views/apps/native_frame_view_mac.h
new file mode 100644
index 0000000000000000000000000000000000000000..f029f81ffeb2eea0125e8f0cc81ae5aed9d5c95e
--- /dev/null
+++ b/chrome/browser/ui/views/apps/native_frame_view_mac.h
@@ -0,0 +1,27 @@
+// 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.
+
+#ifndef CHROME_BROWSER_UI_VIEWS_APPS_NATIVE_FRAME_VIEW_MAC_H_
+#define CHROME_BROWSER_UI_VIEWS_APPS_NATIVE_FRAME_VIEW_MAC_H_
+
+#include "ui/views/window/native_frame_view.h"
+
+class Widget;
+
+class NativeFrameViewMac : public views::NativeFrameView {

[tapted, 2015/03/30 06:33:37]

needs a class comment. It should explain why this is needed (and why just for
app windows).

[jackhou1, 2015/03/31 00:50:42]

Done.

+ public:
+  static const char kViewClassName[];

[tapted, 2015/03/30 06:33:37]

Is this needed for anything? I think it's more common to leave this off for new
view types until it's required to analyse something

[jackhou1, 2015/03/31 00:50:42]

Done.

+
+  explicit NativeFrameViewMac(views::Widget* frame);
+  ~NativeFrameViewMac() override;
+
+  // NonClientFrameView:
+  gfx::Rect GetWindowBoundsForClientBounds(
+      const gfx::Rect& client_bounds) const override;
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(NativeFrameViewMac);
+};
+
+#endif  // CHROME_BROWSER_UI_VIEWS_APPS_NATIVE_FRAME_VIEW_MAC_H_