sync: Implementation of Priority Preferences.

chrome/browser/sync/sync_prefs.cc

Index: chrome/browser/sync/sync_prefs.cc
diff --git a/chrome/browser/sync/sync_prefs.cc b/chrome/browser/sync/sync_prefs.cc
index 2866dd5038192309775a7dfcc8afe85841229591..882467eb76e930934880b5a0c814ec1c4ab35394 100644
--- a/chrome/browser/sync/sync_prefs.cc
+++ b/chrome/browser/sync/sync_prefs.cc
@@ -344,6 +344,8 @@ const char* SyncPrefs::GetPrefNameForDataType(syncer::ModelType data_type) {
       return prefs::kSyncFaviconTracking;
     case syncer::PROXY_TABS:
       return prefs::kSyncTabs;
+    case syncer::PRIORITY_PREFERENCES:
+      return prefs::kSyncPriorityPreferences;

[Mattias Nissler (ping if slow), 2013/03/21 06:50:15]

Is there any migration needed here? I.e. for existing Chrome Profiles that have
Pref sync enabled but nothing else, what should happen if priority prefs become
supported after an update?

[albertb, 2013/03/21 17:10:33]

I'm not sure about this. Nicolas/Tim: what do you think?

[tim (not reviewing), 2013/03/21 18:10:55]

We're not adding a checkbox in the UI for this, right?  So they should just get
enabled as part of prefs (I haven't checked the whole review too closely, but I
assume this is what you / Nicolas did?)

[albertb, 2013/03/21 18:46:29]

Yes, priority preferences are automatically enabled if (normal) preferences are.

     default:
       break;
   }
@@ -409,6 +411,7 @@ void SyncPrefs::RegisterPrefGroups() {
   pref_groups_[syncer::EXTENSIONS].Put(syncer::EXTENSION_SETTINGS);
 
   pref_groups_[syncer::PREFERENCES].Put(syncer::DICTIONARY);
+  pref_groups_[syncer::PREFERENCES].Put(syncer::PRIORITY_PREFERENCES);
   pref_groups_[syncer::PREFERENCES].Put(syncer::SEARCH_ENGINES);
 
   pref_groups_[syncer::TYPED_URLS].Put(syncer::HISTORY_DELETE_DIRECTIVES);