[Sync] Replace about:sync with chrome://sync-internals.

This CL replaces all occurrences of "about:sync" with
"chrome://sync-internals", so the URL is the same everywhere.

Bug: 1137739
Change-Id: I461582da8aa9d809ffe72715d09456fc7818652c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2470077Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Paula Vidas <paulavidas@google.com>
Cr-Commit-Position: refs/heads/master@{#817002}

components/sync/driver/about_sync_util.cc

@@ -80,8 +80,9 @@ namespace {
 
 const char kUninitialized[] = "Uninitialized";
 
-// This class represents one field in about:sync. It gets serialized into a
-// dictionary with entries for 'stat_name', 'stat_value' and 'is_valid'.
+// This class represents one field in chrome://sync-internals. It gets
+// serialized into a dictionary with entries for 'stat_name', 'stat_value' and
+// 'is_valid'.
 class StatBase {
  public:
   base::Value ToValue() const {
@@ -116,8 +117,8 @@ class Stat : public StatBase {
   void Set(const T& value) { SetFromValue(base::Value(value)); }
 };
 
-// A section for display on about:sync, consisting of a title and a list of
-// fields.
+// A section for display on chrome://sync-internals, consisting of a title and a
+// list of fields.
 class Section {
  public:
   Section(const std::string& title, bool is_sensitive)
@@ -301,9 +302,9 @@ std::string GetConnectionStatus(const SyncTokenStatus& status) {
 }  // namespace
 
 // This function both defines the structure of the message to be returned and
-// its contents.  Most of the message consists of simple fields in about:sync
-// which are grouped into sections and populated with the help of the SyncStat
-// classes defined above.
+// its contents.  Most of the message consists of simple fields in
+// chrome://sync-internals which are grouped into sections and populated with
+// the help of the SyncStat classes defined above.
 std::unique_ptr<base::DictionaryValue> ConstructAboutInformation(
     IncludeSensitiveData include_sensitive_data,
     SyncService* service,

components/sync/driver/about_sync_util.h

@@ -70,7 +70,7 @@ extern const char kTypes[];
 using IncludeSensitiveData =
     util::StrongAlias<class IncludeSensitiveDataTag, bool>;
 // This function returns a DictionaryValue which contains all the information
-// required to populate the 'About' tab of about:sync.
+// required to populate the 'About' tab of chrome://sync-internals.
 // Note that |service| may be null.
 // If |include_sensitive_data| is false, Personally Identifiable Information
 // won't be included in the return value.

components/sync/driver/sync_service.h

@@ -419,9 +419,10 @@ class SyncService : public KeyedService {
   // the type's status, and <status> is one of "error", "warning" or "ok"
   // depending on the type's current status.
   //
-  // This function is used by about_sync_util.cc to help populate the about:sync
-  // page.  It returns a ListValue rather than a DictionaryValue in part to make
-  // it easier to iterate over its elements when constructing that page.
+  // This function is used by about_sync_util.cc to help populate the
+  // chrome://sync-internals page.  It returns a ListValue rather than a
+  // DictionaryValue in part to make it easier to iterate over its elements when
+  // constructing that page.
   virtual std::unique_ptr<base::Value> GetTypeStatusMapForDebugging() = 0;
 
   virtual const GURL& GetSyncServiceUrlForDebugging() const = 0;

components/sync/engine/events/protocol_event.h

@@ -20,8 +20,8 @@ namespace syncer {
 // are modelled by {GetUpdates, Commit}x{Request,Response} objects.
 //
 // These objects are intended to be used for displaying information on
-// about:sync.  They should be considered to be immutable and opaque.  No
-// program behavior should depend on their contents.
+// chrome://sync-internals.  They should be considered to be immutable and
+// opaque.  No program behavior should depend on their contents.
 //
 // Each type of request can maintain its own set of additional metadata and have
 // its own custom serialization routines.  For example, the "configure"

components/sync/engine/sync_engine_host.h

@@ -31,8 +31,8 @@ class SyncEngineHost {
   // process changes. If success is false, initialization wasn't able to be
   // completed and should be retried.
   //
-  // |js_backend| is what about:sync interacts with. It is initialized only if
-  // |success| is true.
+  // |js_backend| is what chrome://sync-internals interacts with. It is
+  // initialized only if |success| is true.
 
   virtual void OnEngineInitialized(
       ModelTypeSet initial_types,

components/sync/engine/sync_status.h

@@ -21,7 +21,7 @@ namespace syncer {
 // This struct is closely tied to the AllStatus object which uses instances of
 // it to track and report on the sync engine's internal state, and the functions
 // in sync_ui_util.cc which convert the contents of this struct into a
-// DictionaryValue used to populate the about:sync summary tab.
+// DictionaryValue used to populate the chrome://sync-internals summary tab.
 struct SyncStatus {
   SyncStatus();
   SyncStatus(const SyncStatus& other);

components/sync/engine_impl/all_status.h

@@ -26,12 +26,12 @@ struct SyncCycleEvent;
 // state upon change. It can send to observers a snapshot of this state as a
 // SyncStatus object, aggregating all this data into one place.
 //
-// Most of this data ends up on the about:sync page.  But the page is only
-// 'pinged' to update itself at the end of a sync cycle.  A user could refresh
-// manually, but unless their timing is excellent it's unlikely that a user will
-// see any state in mid-sync cycle.  We have no plans to change this.  However,
-// we will continue to collect data and update state mid-sync-cycle in case we
-// need to debug slow or stuck sync cycles.
+// Most of this data ends up on the chrome://sync-internals page.  But the page
+// is only 'pinged' to update itself at the end of a sync cycle.  A user could
+// refresh manually, but unless their timing is excellent it's unlikely that a
+// user will see any state in mid-sync cycle.  We have no plans to change this.
+// However, we will continue to collect data and update state mid-sync-cycle in
+// case we need to debug slow or stuck sync cycles.
 class AllStatus : public SyncEngineEventListener {
  public:
   AllStatus();

components/sync/engine_impl/sync_manager_impl.h

@@ -186,7 +186,7 @@ class SyncManagerImpl
   bool observing_network_connectivity_changes_;
 
   // Map used to store the notification info to be displayed in
-  // about:sync page.
+  // chrome://sync-internals page.
   NotificationInfoMap notification_info_map_;
 
   // These are for interacting with chrome://sync-internals.

components/sync/js/README

@@ -8,7 +8,7 @@ Much of it has been removed in favor of an ad-hoc system that allows us to
 offer better safety guarantees, and to dispatch requests to different threads.
 
 All that remains are some WeakHandles that allow us to send JsEvents from the
-sync backend to about:sync.  The SyncInternalsUI implements JsEventHandler in
+sync backend to chrome://sync-internals.  The SyncInternalsUI implements JsEventHandler in
 order to receive these events.  The SyncManager implements JsBackend in order
 to send them.  The SyncJsController acts as an intermediary between them.
 

components/sync/model/sync_error.h

@@ -18,7 +18,7 @@ class Location;
 namespace syncer {
 
 // Sync errors are used for debug purposes and handled internally and/or
-// exposed through Chrome's "about:sync" internal page.
+// exposed through Chrome's "chrome://sync-internals" internal page.
 // This class is copy-friendly and thread-safe.
 class SyncError {
  public:

ios/chrome/browser/sync/sync_setup_service.cc

@@ -134,7 +134,7 @@ SyncSetupService::SyncServiceState SyncSetupService::GetSyncServiceState() {
     case GoogleServiceAuthError::NONE:
     // Connection failed is not shown to the user, as this will happen if the
     // service retuned a 500 error. A more detail error can always be checked
-    // on about:sync.
+    // on chrome://sync-internals.
     case GoogleServiceAuthError::CONNECTION_FAILED:
     case GoogleServiceAuthError::USER_NOT_SIGNED_UP:
     case GoogleServiceAuthError::UNEXPECTED_SERVICE_RESPONSE: