chromeos: Add a flag to launch with --mash.

chromeos: Add a flag to launch with --mash.

Add a flag in chrome:flags to turn on the mojo ui service. The caveat
is that it works OK (as in, you can successfully login) if a secondary
user on the device turns on the flag. If the primary user/owner turns
the flag on, then the flag is used in the login screen as well, and
that does not work well yet.

Even though secondary/non-owner users can turn the flag on and login,
and see the chrome browser window (and other mus apps) without getting
immediate crashes, a number of things are still in progress, and not
implemented yet. So there are a number of missing features, and is
somewhat unstable.

BUG=633656
Committed: https://crrev.com/59e835de462f99529c7312b49926e2f0a67aa36e
Cr-Commit-Position: refs/heads/master@{#420219}

[sadrul, 2016-09-20 22:41:38]

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

[sadrul, 2016-09-20 22:42:14]

sadrul@chromium.org changed reviewers:
+ sky@chromium.org

[commit-bot: I haz the power, 2016-09-20 22:42:34]

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, 2016-09-20 22:51:53]

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

[commit-bot: I haz the power, 2016-09-20 22:51:54]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[sky, 2016-09-20 22:54:23]

Is this flag may leave you in a hosed state can you make it so we only honor
--mash if on canary or dev builds?

[sadrul, 2016-09-21 02:08:11]

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

[commit-bot: I haz the power, 2016-09-21 02:08:40]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[sadrul, 2016-09-21 02:09:02]

On 2016/09/20 22:54:23, sky wrote:
> Is this flag may leave you in a hosed state can you make it so we only honor
> --mash if on canary or dev builds?

Done.

[commit-bot: I haz the power, 2016-09-21 02:53:41]

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

[commit-bot: I haz the power, 2016-09-21 02:53:41]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[sky, 2016-09-21 02:54:51]

LGTM

[sadrul, 2016-09-21 22:22:40]

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

[commit-bot: I haz the power, 2016-09-21 22:23:10]

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, 2016-09-21 23:25:23]

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

[commit-bot: I haz the power, 2016-09-21 23:25:24]

Dry run: This issue passed the CQ dry run.

[sadrul, 2016-09-22 00:20:33]

sadrul@chromium.org changed reviewers:
+ isherman@chromium.org

[sadrul, 2016-09-22 00:20:34]

+isherman@ for histograms.xml

[Ilya Sherman, 2016-09-22 00:48:31]

histograms.xml lgtm

[sadrul, 2016-09-22 00:52:44]

The CQ bit was checked by sadrul@chromium.org

[sadrul, 2016-09-22 00:52:44]

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

[commit-bot: I haz the power, 2016-09-22 00:53:26]

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, 2016-09-22 00:59:52]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-09-22 01:02:38]

Description was changed from

==========
chromeos: Add a flag to launch with --mash.

Add a flag in chrome:flags to turn on the mojo ui service. The caveat
is that it works OK (as in, you can successfully login) if a secondary
user on the device turns on the flag. If the primary user/owner turns
the flag on, then the flag is used in the login screen as well, and
that does not work well yet.

Even though secondary/non-owner users can turn the flag on and login,
and see the chrome browser window (and other mus apps) without getting
immediate crashes, a number of things are still in progress, and not
implemented yet. So there are a number of missing features, and is
somewhat unstable.

BUG=633656
==========

to

==========
chromeos: Add a flag to launch with --mash.

Add a flag in chrome:flags to turn on the mojo ui service. The caveat
is that it works OK (as in, you can successfully login) if a secondary
user on the device turns on the flag. If the primary user/owner turns
the flag on, then the flag is used in the login screen as well, and
that does not work well yet.

Even though secondary/non-owner users can turn the flag on and login,
and see the chrome browser window (and other mus apps) without getting
immediate crashes, a number of things are still in progress, and not
implemented yet. So there are a number of missing features, and is
somewhat unstable.

BUG=633656

Committed: https://crrev.com/59e835de462f99529c7312b49926e2f0a67aa36e
Cr-Commit-Position: refs/heads/master@{#420219}
==========

[commit-bot: I haz the power, 2016-09-22 01:02:40]

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