Expose kDeviceLoginScreenDomainAutoComplete through CrosSettings

chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc

Index: chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc
diff --git a/chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc b/chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc
index bfc5b14666ff5753cc63e5c249628475e7629644..19dcb302cc36f42900cdec6b7f5f8e5b6dbdf4cc 100644
--- a/chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc
+++ b/chrome/browser/chromeos/policy/device_policy_decoder_chromeos.cc
@@ -595,18 +595,6 @@ void DecodeAccessibilityPolicies(const em::ChromeDeviceSettingsProto& policy,
               container.login_screen_default_virtual_keyboard_enabled()),
           NULL);
     }
-
-    // The behavior when policy is not set and when it is set to an empty string
-    // is the same. Thus lets add policy to the map only if it is set and its
-    // value is not an empty string.
-    if (container.has_login_screen_domain_auto_complete() &&
-        !container.login_screen_domain_auto_complete().empty()) {

[Andrew T Wilson (Slow), 2015/04/01 13:33:21]

I think you may still want some code like this to set the policy in the policy
map regardless. Maybe ping mattias about whether we actually should remove this
entirely?

[peletskyi, 2015/04/01 13:55:19]

I will add Mattias as a reviewer.

-      policies->Set(
-          key::kDeviceLoginScreenDomainAutoComplete, POLICY_LEVEL_MANDATORY,
-          POLICY_SCOPE_MACHINE,
-          new base::StringValue(container.login_screen_domain_auto_complete()),
-          nullptr);
-    }
   }
 }