Apply default wallpaper from customization manifest.

chrome/browser/chromeos/login/wizard_controller.cc

Index: chrome/browser/chromeos/login/wizard_controller.cc
diff --git a/chrome/browser/chromeos/login/wizard_controller.cc b/chrome/browser/chromeos/login/wizard_controller.cc
index 059084e5e1c9c418ca2c590b811ad0226ad7c212..d155ff6a621f9516af63dba7f4ad5caa27a5257e 100644
--- a/chrome/browser/chromeos/login/wizard_controller.cc
+++ b/chrome/browser/chromeos/login/wizard_controller.cc
@@ -652,6 +652,7 @@ void WizardController::PerformPostEulaActions() {
       base::Bind(&WizardController::StartTimezoneResolve,
                  weak_factory_.GetWeakPtr()),
       base::TimeDelta::FromMilliseconds(kDefaultNetworkRetryDelayMS));
+  ServicesCustomizationDocument::GetInstance()->StartFetching();

[Nikita (slow), 2014/04/15 12:39:24]

Is this the only place where StartFetching() is called?

If OEM wallpaper download fails here for network connectivity reasons, when it
will retry?

[Alexander Alekseev, 2014/04/15 22:47:31]

As far as I understand, customization will be additionally fetched for each new
user on device, so customization will be fetched this of other way.

The problem is that
ServicesCustomizationDocument::GetInstance()->CheckAndApplyWallpaper()
should be called on each boot and I didn't find a proper place to
insert this call.

[Dmitry Polukhin, 2014/04/15 22:57:06]

I think it should be somewhere near ShowLoginWizard. But please make sure that
manifest is not fetched before ELUA accepted.

[Nikita (slow), 2014/04/16 18:16:21]

Please make sure that customization document header comment includes this
details i.e. when oem wallpaper fetch happens and when it will be retried.

Same goes about comparing existing URL with new one if it is changed.
Do we actually support now refetching manifest or not?

[Alexander Alekseev, 2014/04/16 23:19:59]

Done.

[Alexander Alekseev, 2014/04/16 23:19:59]

There is a comment on no-refetch policy here:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chr...

I've added another comment on this to the header file.

 
   // Now that EULA has been accepted (for official builds), enable portal check.
   // ChromiumOS builds would go though this code path too.