Re-enable fetching component policies for login screen apps

chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h

Index: chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h
diff --git a/chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h b/chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h
index 7a30322ceee7f429be3d66b31bbfab09997e0834..a7a734c21e73f110d4e57da53f2df08c0f8522b8 100644
--- a/chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h
+++ b/chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h
@@ -176,11 +176,7 @@ class DeviceCloudPolicyManagerChromeOS : public CloudPolicyManager {
       signin_profile_forwarding_schema_registry_;
 
   // Whether the component cloud policy service should be created.
-  // TODO(emaxx): Change the default to true once both the client and the
-  // DMServer are ready for handling policy fetches with the
-  // google/chromeos/signinextension type. See crbug.com/666720,
-  // crbug.com/644304 for reference.
-  bool is_component_policy_enabled_ = false;
+  bool is_component_policy_enabled_ = true;

[Thiemo Nagel, 2016/12/29 17:05:21]

Nit: Maybe it would make sense to change polarity and rename to
"disable_component_policy_for_testing_"?

[emaxx, 2016/12/30 03:24:27]

Done. (Finally named "component_policy_disabled_for_testing".)

 
   base::ObserverList<Observer, true> observers_;