[MD Settings][People] Visual updates to the sync setup page.

chrome/browser/ui/webui/settings/people_handler.cc

Index: chrome/browser/ui/webui/settings/people_handler.cc
diff --git a/chrome/browser/ui/webui/settings/people_handler.cc b/chrome/browser/ui/webui/settings/people_handler.cc
index 55ebfe8cc730bdb06ba1a7e24bf6a7ee4473c378..42911c428336fa92f0b895d1458edc5cebfebf68 100644
--- a/chrome/browser/ui/webui/settings/people_handler.cc
+++ b/chrome/browser/ui/webui/settings/people_handler.cc
@@ -868,9 +868,6 @@ void PeopleHandler::PushSyncPrefs() {
   } else if (passphrase_type == syncer::PassphraseType::CUSTOM_PASSPHRASE) {
     args.SetString("fullEncryptionBody",
                    GetStringUTF16(IDS_SYNC_FULL_ENCRYPTION_BODY_CUSTOM));
-  } else {
-    args.SetString("fullEncryptionBody",

[tommycli, 2016/10/25 18:28:46]

Why was this removed? Is this string never used?

-                   GetStringUTF16(IDS_SYNC_FULL_ENCRYPTION_DATA));

[Moe, 2016/10/25 22:30:18]

I don't think this was ever necessary. This string is identical to
'encryptWithSyncPassphraseLabel' which is used in
https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/people...
if fullEncryptionBody isn't set.
Since the string in the mocks seems to have a hyperlink, in order to avoid the
inner-h-t-m-l hack, I changed the logic by not setting the fullEncryptionBody
here and instead use encryptWithSyncPassphraseLabel directly in sync_page.html

   }
 
   CallJavascriptFunction("cr.webUIListenerCallback",