summaryrefslogtreecommitdiffstats
path: root/chrome/browser/extensions/api/app_window/app_window_api.cc
diff options
context:
space:
mode:
authorbshe@chromium.org <bshe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-12-11 21:45:48 +0000
committerbshe@chromium.org <bshe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-12-11 21:45:48 +0000
commit6ed36cd11e0b800f273548cf5eaf2cb97969a4c7 (patch)
treebdfe9fa11b130598394d7f4b8c8d5f89e3b09be8 /chrome/browser/extensions/api/app_window/app_window_api.cc
parentebaa018d735b4eb278f671c5735d1f998db5757d (diff)
downloadchromium_src-6ed36cd11e0b800f273548cf5eaf2cb97969a4c7.zip
chromium_src-6ed36cd11e0b800f273548cf5eaf2cb97969a4c7.tar.gz
chromium_src-6ed36cd11e0b800f273548cf5eaf2cb97969a4c7.tar.bz2
Callback to function InitializeRegisteredDeviceWallpaper after cros settings can be trusted
InitializeWallpaper is being called in a very early stage(shell initialization). At such point, the cros settings may not be validated, so the value maybe wrong. Function InitializeWallpaper, however, depends on kAccountsPrefShowUserNamesOnSignIn to behavior correctly. This CL made a callback to InitializeWallpaper if we detect that the settings is not yet validated. BUG=162760 Review URL: https://codereview.chromium.org/11299304 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172415 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/extensions/api/app_window/app_window_api.cc')
0 files changed, 0 insertions, 0 deletions