Clarified description of the timezone policy.

chrome/browser/policy/proto/chrome_device_policy.proto

Index: chrome/browser/policy/proto/chrome_device_policy.proto
diff --git a/chrome/browser/policy/proto/chrome_device_policy.proto b/chrome/browser/policy/proto/chrome_device_policy.proto
index 262e85eec4db62e1e7715f0339f04c5dfd5f3dac..55f0d250cc9041d4a09d3fecd75c729641cacb93 100644
--- a/chrome/browser/policy/proto/chrome_device_policy.proto
+++ b/chrome/browser/policy/proto/chrome_device_policy.proto
@@ -207,10 +207,16 @@ message StartUpUrlsProto {
 }
 
 message SystemTimezoneProto {
-  // Specifies the timezone which is applied if this value is provided. Valid
-  // values are listed in "timezone_settings.cc". Additionally, timezones from
-  // the "IANA Time Zone Database" (e.g. listed on wikipedia) that are
-  // equivalent to one of the timezones in "timezone_settings.cc" are valid.
+  // Specifies an owner-determined timezone that applies to the login screen and
+  // all users. Valid values are listed in "timezone_settings.cc". Additionally,
+  // timezones from the "IANA Time Zone Database" (e.g. listed on wikipedia)
+  // that are equivalent to one of the timezones in "timezone_settings.cc" are
+  // valid. In case of an invalid value, the setting is still activated with a
+  // fallback timezone (currently "GMT").
+  // Only if no value is provided, the timezone device setting is inactive. In

[Bin, 2012/08/21 17:05:22]

No value means the optional value is not set. An empty string is considered as
an invalid value, right? It may worthwhile explicitly stating it out.

[pneubeck (no reviews), 2012/08/22 07:39:41]

Done.

+  // that case, the currently active timezone will remain in use however users
+  // can change the timezone and the change is persistent. Thus a change by one
+  // user affects the login-screen and all other users.
   optional string timezone = 1;
 }