[Chrome OS] Fix storing of proxy information on Chrome OS
commitdd5a8b3832dbe4b26541c68014aecb65515c8e57
authorcmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 21 Apr 2011 11:02:26 +0000 (21 11:02 +0000)
committercmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 21 Apr 2011 11:02:26 +0000 (21 11:02 +0000)
treefbf66f1f74d26cc174a5c41e91084170a48015db
parent03e389432fd984cc448c790fa9363053c4895317
[Chrome OS] Fix storing of proxy information on Chrome OS

DCHECK()s are not compiled in non-Debug builds.  Any statement inside a DCHECK() will therefore not occur
on Release builds :-)
When persisting proxy information via the SignedSettings API, the call that stuffed the proxy info
into the policy we ultimately send out over DBus was wrapped in a DCHECK()

BUG=chromium-os:14326
TEST=manual, unit_tests

R=mnissler@chromium.org

Review URL: http://codereview.chromium.org/6880102

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82469 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/chromeos/login/signed_settings.cc
chrome/browser/chromeos/login/signed_settings_unittest.cc