Remove the initial delay when first entering immersive fullscreen in a PWA.

Remove the initial delay when first entering immersive fullscreen in a PWA.

On first launch, PWAs open a splash screen. If the PWA is set to open in
immersive fullscreen via the manifest property display: fullscreen, the
splash screen currently opens in standalone non-immersive mode before
the PWA transitions to immersive mode. At the point of transition, the
splash screen icon "jumps" as the view resizes.

This CL addresses this problem by transitioning immediately to immersive
fullscreen before loading the splash screen. Now the splash screen opens
directly into immersive fullscreen, removing any resizing.

BUG=720174
Review-Url: https://codereview.chromium.org/2869283002
Cr-Commit-Position: refs/heads/master@{#470746}
Committed: https://chromium.googlesource.com/chromium/src/+/d7631c332aae8ba4281325a4955e5a46e8b857f7

[dominickn, 2017-05-10 01:13:32]

The CQ bit was checked by dominickn@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-10 01:14:27]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 03:16:26]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-10 03:16:26]

Dry run: Try jobs failed on following builders:
  cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has
not started yet; builder either lacks capacity or does not exist (misspelled?))
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet;
builder either lacks capacity or does not exist (misspelled?))
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does
not exist (misspelled?))
  chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, build
has not started yet; builder either lacks capacity or does not exist
(misspelled?))
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT,
build has not started yet; builder either lacks capacity or does not exist
(misspelled?))
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does
not exist (misspelled?))
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does
not exist (misspelled?))
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does
not exist (misspelled?))
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, build
has not started yet; builder either lacks capacity or does not exist
(misspelled?))

[dominickn, 2017-05-10 03:38:36]

dominickn@chromium.org changed reviewers:
+ tedchoc@chromium.org

[dominickn, 2017-05-10 03:38:36]

PTAL, thanks!

[Ted C, 2017-05-10 14:42:57]

lgtm

[dominickn, 2017-05-10 23:20:07]

The CQ bit was checked by dominickn@chromium.org

[commit-bot: I haz the power, 2017-05-10 23:21:14]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 23:32:58]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494458407207330, "parent_rev":
"6c4024f15794934a9f99a1d1dae4cad29ed9124c", "commit_rev":
"d7631c332aae8ba4281325a4955e5a46e8b857f7"}

[commit-bot: I haz the power, 2017-05-10 23:33:08]

Description was changed from

==========
Remove the initial delay when first entering immersive fullscreen in a PWA.

On first launch, PWAs open a splash screen. If the PWA is set to open in
immersive fullscreen via the manifest property display: fullscreen, the
splash screen currently opens in standalone non-immersive mode before
the PWA transitions to immersive mode. At the point of transition, the
splash screen icon "jumps" as the view resizes.

This CL addresses this problem by transitioning immediately to immersive
fullscreen before loading the splash screen. Now the splash screen opens
directly into immersive fullscreen, removing any resizing.

BUG=720174
==========

to

==========
Remove the initial delay when first entering immersive fullscreen in a PWA.

On first launch, PWAs open a splash screen. If the PWA is set to open in
immersive fullscreen via the manifest property display: fullscreen, the
splash screen currently opens in standalone non-immersive mode before
the PWA transitions to immersive mode. At the point of transition, the
splash screen icon "jumps" as the view resizes.

This CL addresses this problem by transitioning immediately to immersive
fullscreen before loading the splash screen. Now the splash screen opens
directly into immersive fullscreen, removing any resizing.

BUG=720174

Review-Url: https://codereview.chromium.org/2869283002
Cr-Commit-Position: refs/heads/master@{#470746}
Committed:
https://chromium.googlesource.com/chromium/src/+/d7631c332aae8ba4281325a4955e...
==========

[commit-bot: I haz the power, 2017-05-10 23:33:13]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/d7631c332aae8ba4281325a4955e...