MD Settings: cr/cros - Guest mode page visibility

chrome/browser/resources/settings/date_time_page/date_time_page.html

Index: chrome/browser/resources/settings/date_time_page/date_time_page.html
diff --git a/chrome/browser/resources/settings/date_time_page/date_time_page.html b/chrome/browser/resources/settings/date_time_page/date_time_page.html
index f8d788d2822908d57f21f9a20e1f1e3824c82d0f..f0c8f0753bf12226e317982cab13c3256468ffb2 100644
--- a/chrome/browser/resources/settings/date_time_page/date_time_page.html
+++ b/chrome/browser/resources/settings/date_time_page/date_time_page.html
@@ -7,7 +7,9 @@
   <template>
     <style include="settings-shared"></style>
     <div class="settings-box first block">
-      <div>$i18n{timeZone}</div>
+      <div disabled$="[[!pageVisibility.timeZoneSelector]]">

[dpapad, 2016/07/22 22:40:48]

+michaelpg

Are we OK with having HTML refer to Polymer properties that are not defined in
the |properties| section of the equivalent JS file (referring to
|pageVisibility| variable)?

[Moe, 2016/07/24 23:54:26]

I think after introducing the sub-types it won't hurt to declare the properties
in the JS.

+        $i18n{timeZone}
+      </div>
       <settings-checkbox pref="{{prefs.settings.clock.use_24hour_clock}}"
           label="$i18n{use24HourClock}">
       </settings-checkbox>