Disabled metro mode launch for Windows 10, until there some clarity on technical details.

Disabled metro mode launch for Windows 10, until there is some clarity on technical details.
Note: You can still launch and test using either --force-immersive command line or by pressing Shift+F11 magic key just after launching chrome through shortcut.

BUG=470227
R=cpu,ananta

Committed: https://crrev.com/a96f46b821b7c9400ffb14462ad87c33be547407
Cr-Commit-Position: refs/heads/master@{#324363}

[cpu_(ooo_6.6-7.5), 2015-03-26 20:13:33]

Like hidding the menu, but we should allow some way for launching it, so we can
test from time to time.

[Shrikant Kelkar, 2015-03-26 20:32:15]

On 2015/03/26 20:13:33, cpu wrote:
> Like hidding the menu, but we should allow some way for launching it, so we
can
> test from time to time.

Ack, enabled --force-immersive and Shift+F11 magic key. On Win10 we won't use
persisted state, that will help users get out of chrome-invisible mode.
ptal.

[Shrikant Kelkar, 2015-03-26 22:04:23]

The CQ bit was checked by shrikant@chromium.org

[Shrikant Kelkar, 2015-03-26 22:04:24]

The CQ bit was unchecked by shrikant@chromium.org

[Shrikant Kelkar, 2015-04-01 21:14:19]

On 2015/03/26 20:32:15, Shrikant Kelkar wrote:
> On 2015/03/26 20:13:33, cpu wrote:
> > Like hidding the menu, but we should allow some way for launching it, so we
> can
> > test from time to time.
> 
> Ack, enabled --force-immersive and Shift+F11 magic key. On Win10 we won't use
> persisted state, that will help users get out of chrome-invisible mode.
> ptal.

ping

[cpu_(ooo_6.6-7.5), 2015-04-09 00:42:47]

lgtm

[Shrikant Kelkar, 2015-04-09 00:52:16]

The CQ bit was checked by shrikant@chromium.org

[commit-bot: I haz the power, 2015-04-09 00:53:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1015533014/20001

[commit-bot: I haz the power, 2015-04-09 01:05:09]

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

[commit-bot: I haz the power, 2015-04-09 01:05:10]

Try jobs failed on following builders:
  linux_chromium_compile_dbg_32_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  win8_chromium_rel on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)

[Shrikant Kelkar, 2015-04-09 01:59:49]

The CQ bit was checked by shrikant@chromium.org

[Shrikant Kelkar, 2015-04-09 01:59:49]

The patchset sent to the CQ was uploaded after l-g-t-m from cpu@chromium.org
Link to the patchset: https://codereview.chromium.org/1015533014/#ps40001
(title: "Rebased")

[commit-bot: I haz the power, 2015-04-09 02:02:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1015533014/40001

[commit-bot: I haz the power, 2015-04-09 04:11:03]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-04-09 04:11:54]

Patchset 3 (id:??) landed as
https://crrev.com/a96f46b821b7c9400ffb14462ad87c33be547407
Cr-Commit-Position: refs/heads/master@{#324363}