Settings People Revamp: Update main card Sync 'look' to match new spec.

chrome/browser/resources/settings/people_page/people_page.js

 // 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.
 
 /**
  * @fileoverview
  * 'settings-people-page' is the settings page containing sign-in settings.
  */
 Polymer({
   is: 'settings-people-page',
@@ skipping 131 matching lines @@
     this.profileName_ = info.name;
     this.profileIconUrl_ = info.iconUrl;
   },
 
   /**
    * Handler for when the sync state is pushed from the browser.
    * @private
    */
   handleSyncStatus_: function(syncStatus) {
     this.syncStatus = syncStatus;
-
-    // TODO(tommycli): Remove once we figure out how to refactor the sync
-    // code to not include HTML in the status messages.
-    this.$.syncStatusText.innerHTML = syncStatus.statusText;
   },
 
 <if expr="chromeos">
   /**
    * Handler for when the Easy Unlock enabled status has changed.
    * @private
    */
   handleEasyUnlockEnabledStatusChanged_: function(easyUnlockEnabled) {
     this.easyUnlockEnabled_ = easyUnlockEnabled;
   },
@@ skipping 34 matching lines @@
   /** @private */
   onDisconnectConfirm_: function() {
     var deleteProfile = this.$.deleteProfile && this.$.deleteProfile.checked;
     this.syncBrowserProxy_.signOut(deleteProfile);
 
     // Dialog automatically closed because button has dialog-confirm attribute.
   },
 
   /** @private */
   onSyncTap_: function() {
+    if (!this.syncStatus.signedIn || this.syncStatus.managed ||
+        !this.syncStatus.syncSystemEnabled) {

[dschuyler, 2016/05/18 00:08:00]

Can these reasonably happen?
Or is this action unavailable in these states?

Can we make it so that this action cannot be
initiated (rather than blocked here) in those
situations?

[tommycli, 2016/05/18 18:31:46]

Done. I made the two that can't reasonably happen to be assertions. I made the
one case that can happen to be 'managed'.

Hypothetically, we could remove the event handler if syncStatus.managed, but I
think this is a cleaner solution than to be adding and removing event handlers.

+      return;
+    }
+
     this.$.pages.setSubpageChain(['sync']);
   },
 
 <if expr="chromeos">
   /** @private */
   onEasyUnlockSetupTap_: function() {
     this.easyUnlockBrowserProxy_.startTurnOnFlow();
   },
 
   /** @private */
   onEasyUnlockTurnOffTap_: function() {
     this.$$('#easyUnlockTurnOffDialog').open();
   },
 </if>
 
   /** @private */
   onManageOtherPeople_: function() {
 <if expr="not chromeos">
     this.syncBrowserProxy_.manageOtherPeople();
 </if>
 <if expr="chromeos">
     this.$.pages.setSubpageChain(['users']);
 </if>
   },
 
   /**
    * @private

[dschuyler, 2016/05/18 00:08:00]

@param for syncStatus

[tommycli, 2016/05/18 18:31:46]

Done.

    * @return {boolean}
    */
-  isStatusTextSet_: function(syncStatus) {
-    return syncStatus && syncStatus.statusText.length > 0;
+  isAdvancedSyncSettingsVisible_: function(syncStatus) {
+    return syncStatus && syncStatus.signedIn && syncStatus.syncSystemEnabled;
   },
 
   /**
    * @private

[dschuyler, 2016/05/18 00:08:00]

@param for syncStatus

[tommycli, 2016/05/18 18:31:46]

Done.

-   * @return {boolean}
+   * @return {string}
    */
-  isAdvancedSyncSettingsVisible_: function(syncStatus) {
-    return syncStatus && syncStatus.signedIn && !syncStatus.managed &&
-           syncStatus.syncSystemEnabled;
+  getSyncIcon_: function(syncStatus) {
+    if (!syncStatus)
+      return '';
+    if (syncStatus.hasError)
+      return 'settings:sync-problem';
+    if (syncStatus.managed)
+      return 'settings:sync-disabled';
+
+    return 'settings:done';
+  },
+
+  /**
+   * @private

[dschuyler, 2016/05/18 00:08:00]

@param

[tommycli, 2016/05/18 18:31:46]

Done.

+   * @return {string}
+   */
+  getSyncStatusClass_: function(syncStatus) {
+    return (syncStatus && syncStatus.hasError) ? 'sync-error' : '';
   },
 });