Move printing.* prefs from local state to profile

chrome/browser/profiles/profile_impl.cc

Index: chrome/browser/profiles/profile_impl.cc
diff --git a/chrome/browser/profiles/profile_impl.cc b/chrome/browser/profiles/profile_impl.cc
index 36e24cb81346853aacea9b1fc9952951babe1eec..634940ae42aaa943b99fb5eb05abfb70c36d4619 100644
--- a/chrome/browser/profiles/profile_impl.cc
+++ b/chrome/browser/profiles/profile_impl.cc
@@ -221,6 +221,18 @@ void ProfileImpl::RegisterUserPrefs(PrefService* prefs) {
   prefs->RegisterStringPref(prefs::kHomePage,
                             std::string(),
                             PrefService::SYNCABLE_PREF);
+#if defined(ENABLE_PRINTING)
+  prefs->RegisterBooleanPref(prefs::kPrintingEnabled,

[Albert Bodenhamer, 2012/07/18 17:00:10]

PrintingEnabled is driven by device policy.  Does it make sense as a user pref?

[bartfab (slow), 2012/07/18 17:18:30]

The pref exists as a vehicle for policy: Policy sets pref, pref influences
Chrome. The pref is not exposed to the user but it must exist in the background.
It did exist already but was registered per-user. Now it is registered
per-profile. This makes no practical difference right now but if we want to, we
can actually give users finer grained control in the far future: We could enable
and disable printing on a per-profile basis.

[Albert Bodenhamer, 2012/07/18 17:23:20]

Sounds good.
On 2012/07/18 17:18:30, bartfab wrote:

+                             true,
+                             PrefService::UNSYNCABLE_PREF);
+#endif
+  prefs->RegisterBooleanPref(prefs::kPrintPreviewDisabled,
+#if defined(GOOGLE_CHROME_BUILD)
+                             false,
+#else
+                             true,
+#endif
+                             PrefService::UNSYNCABLE_PREF);
 
   // Initialize the cache prefs.
   prefs->RegisterFilePathPref(prefs::kDiskCacheDir,