GitLab

The goal is to show screensaver immediately after demo session logs in.
In order to avoid the visual delay during the screensaver installation,
we need to:

1. Bypass install_limiter: it's reasonable to make an exception for
   the screensaver app during demo mode. The choices for the size limit
   (1MB) and the delay (5000 ms) are somewhat arbitrary in the first
   place. We'd still like to keep the install limiter in all other
   cases unless there's a real need to bypass it, ie:
   1) All other apps during demo mode,
   2) The screensaver app in non-demo mode (only possible if people
      randomly find it from the web store.)
   3) All other apps in non-demo mode (the majority cases).

2. Initiate installation earlier: if we wait until session state
   becomes active, then its installation will happen later than the
   policy forced ones. Instead, we can observe the profile creation
   and start installation right after profile is created.

   Highlights app should be installed at the same time, but do not
   change it for now because:

   1) Before we disable browser launch for demo sessions, we want
      Highlights app to appear between the screensaver and the
      browser window. This is hard to achieve if installing Highlights
      app at the same time with screensaver (which happens before
      browser launch).

   2) Installing another large app may affect installing the
      screensaver.


Bug: 870851
Change-Id: Ia8f7bb4f02d69e73a4c79839531ee1c190414d3d
Reviewed-on: https://chromium-review.googlesource.com/1212448
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592307}