Implemented ForceMaximizeBrowserWindowOnFirstRun policy, added unit test and browser test.

components/policy/resources/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 105 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 289
+#   For your editing convenience: highest ID currently used: 290
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 6988 matching lines @@
       'device_only': True,
       'features': {
         'dynamic_refresh': True,
       },
       'example_value': True,
       'id': 284,
       'caption': '''Automatic reboot on device shutdown''',
       'desc': '''If this policy is set to false or not configured, <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> will allow the user to shut down the device.
       If this policy is set to true, <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> will trigger a reboot when the user shuts down the device. <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> replaces all occurrences of shutdown buttons in the UI by reboot buttons. If the user shuts down the device using the power button, it will not automatically reboot, even if the policy is enabled.''',
     },
+    {
+      'name': 'ForceMaximizeBrowserWindowOnFirstRun',

[bartfab (slow), 2015/03/12 11:54:48]

Nit: How about s/BrowserWindow//? It seems unnecessary.

[peletskyi, 2015/03/18 13:28:13]

Done.

+      'type': 'main',
+      'schema': { 'type': 'boolean' },
+      'supported_on': ['chrome_os:41-'],

[bartfab (slow), 2015/03/12 11:54:48]

Nit: s/41/43/

[peletskyi, 2015/03/18 13:28:13]

Done.

+      'features': {
+        'dynamic_refresh': False,
+        'per_profile': True,
+      },
+      'example_value': True,
+      'id': 290,
+      'caption': '''Maximize browser window on the first run''',

[bartfab (slow), 2015/03/12 11:54:48]

Nit 1: s/browser/the first browser/
Nit 2: s/the //

[peletskyi, 2015/03/18 13:28:13]

Done.

+      'desc': '''If this policy is set to true <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> will be launched in maximized mode on the first run or on each login in case of public sessions.

[bartfab (slow), 2015/03/12 11:54:48]

Nit 1: s/true/true,/
Nit 2: s/be launched in maximized mode on the/unconditionally maximize the the
first window shown on/
Nit 3: I think we can remove the " or on each login in case of public sessions
bit." It is not just public sessions that behave this way. Ephemeral user
sessions are also always considered to be doing a "first login."

[peletskyi, 2015/03/18 13:28:13]

Done.

+      If this policy is set to false or not configured <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> will be opened in default mode (maximized in case if screen width less than 1366 in case of first run or as in previous run).''',

[bartfab (slow), 2015/03/12 11:54:48]

Nit 1: s/configured/configured,/
Nit 2: I think you can simplify this to: "a heuristic will decide whether to
maximize the first window shown, based on the screen size." There is no need to
refer to a "previous run" here as by definition, we are looking at first runs
only.

[peletskyi, 2015/03/18 13:28:13]

Done.

+    },
   ],
   'messages': {
     # Messages that are not associated to any policies.
     'win_supported_winxpsp2': {
       'desc': '''A label specifying the oldest possible compatible version of Windows. This text will appear right next to a label containing the text 'Supported on:'.''',
       'text': '''Microsoft Windows XP SP2 or later'''
     },
     'mac_chrome_preferences': {
       'desc': '''A text indicating in Mac OS X Workgroup Manager, that currently the preferences of Chromium are being edited''',
       'text': '''<ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> preferences'''
@@ skipping 104 matching lines @@
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
     'doc_complex_policies_on_windows': {
       'desc': '''Text pointing the user to a help article for complex policies on Windows''',
       'text': '''encoded as a JSON string, for details see <ph name="COMPLEX_POLICIES_URL">http://www.chromium.org/administrators/complex-policies-on-windows<ex>http://www.chromium.org/administrators/complex-policies-on-windows</ex></ph>''',
     },
   },
   'placeholders': [],
 }