ChromeOS: Add SystemTimezoneAutomaticDetection policy.

chrome/browser/chromeos/policy/proto/chrome_device_policy.proto

Index: chrome/browser/chromeos/policy/proto/chrome_device_policy.proto
diff --git a/chrome/browser/chromeos/policy/proto/chrome_device_policy.proto b/chrome/browser/chromeos/policy/proto/chrome_device_policy.proto
index 9de8517907fbbe85c59903ce177cc13d48c9a933..62772bec0975bfb6ff36218e60dfa7ff17c450c8 100644
--- a/chrome/browser/chromeos/policy/proto/chrome_device_policy.proto
+++ b/chrome/browser/chromeos/policy/proto/chrome_device_policy.proto
@@ -687,6 +687,20 @@ message AllowBluetoothProto {
   optional bool allow_bluetooth = 1 [default = true];
 }
 
+message SystemTimezoneAutomaticDetectionProto {

[cschuet (SLOW), 2016/03/30 13:08:48]

Rather than creating a new submessage for just this policy stick it into the
existing SystemTimezoneProto message.

[Alexander Alekseev, 2016/03/31 06:51:49]

I will try, but this seems to be tricky.
SystemTimezone is not mapped to any Local State preference.
It was implemented before automatic mappings were implemented.
We also do not have any tests for SystemTimezone.

+  // This allows domain administrators to control the timezone settings for
+  // their devices.
+  enum AutomaticTimezoneDetectionType {
+    USERS_DECIDE = 0;
+    DISABLED = 1;
+    IP_ONLY = 2;
+    SEND_WIFI_ACCESS_POINTS = 3;
+    SEND_WIFI_ACCESS_POINTS_TEST = 4;
+  };
+
+  optional AutomaticTimezoneDetectionType timezone_detection_type = 1;
+}
+
 message ChromeDeviceSettingsProto {
   optional DevicePolicyRefreshRateProto device_policy_refresh_rate = 1;
   optional UserWhitelistProto user_whitelist = 2;
@@ -736,4 +750,6 @@ message ChromeDeviceSettingsProto {
   optional LoginAuthenticationBehaviorProto login_authentication_behavior = 41;
   optional UsbDetachableWhitelistProto usb_detachable_whitelist = 42;
   optional AllowBluetoothProto allow_bluetooth = 43;
+  optional SystemTimezoneAutomaticDetectionProto
+      system_timezone_automatic_detection = 44;
 }