mash: Makes mash and service:ui not establish outgoing connections

mash: Makes mash and service:ui not establish outgoing connections

The ui service was connecting to chrome for the ime driver. As the ui
service is a singleton and chrome isn't, this triggered launching
another process of chrome, which we don't want. Turns out having ui
connect to chrome for the ime driver is unnecessary as chrome already
does this. So, removing the code.

Mash was connecting to the chrome for the keyboard service. This is
also problematic for similar reasons, so removing it too. Filed bug
to have chrome register keyboard with mash.

BUG=664267, 662157, 664264, 683192, 683289
TEST=none
R=moshayedi@chromium.org

Review-Url: https://codereview.chromium.org/2645683007
Cr-Commit-Position: refs/heads/master@{#445172}
Committed: https://chromium.googlesource.com/chromium/src/+/1340ff2da37b5fcd669e08842cea9223b325a873

[sky, 2017-01-20 19:28:57]

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

[commit-bot: I haz the power, 2017-01-20 19:29:39]

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

[Hadi, 2017-01-20 19:45:15]

Do we still require "service:catalog" in services/ui/manifest.json?

[sky, 2017-01-20 20:29:22]

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

[commit-bot: I haz the power, 2017-01-20 20:29:48]

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

[sky, 2017-01-20 20:31:10]

On 2017/01/20 19:45:15, Hadi wrote:
> Do we still require "service:catalog" in services/ui/manifest.json?

We do need catalog as services/ui/service.cc connects to catalog, but the
category name was wrong. I fixed it.

[sky, 2017-01-20 20:39:26]

Description was changed from

==========
mash: Makes mash and service:ui not establish outgoing connections

The ui service was connecting to chrome for the ime driver. As the ui
service is a singleton and chrome isn't, this triggered launching
another process of chrome, which we don't want. Turns out having ui
connect to chrome for the ime driver is unnecessary as chrome already
does this. So, removing the code.

Mash was connecting to the chrome for the keyboard service. This is
also problematic for similar reasons, so removing it too. Filed bug
to have chrome register keyboard with mash.

BUG=664267 662157 664264 683192 683289
TEST=none
R=moshayedi@chromium.org
==========

to

==========
mash: Makes mash and service:ui not establish outgoing connections

The ui service was connecting to chrome for the ime driver. As the ui
service is a singleton and chrome isn't, this triggered launching
another process of chrome, which we don't want. Turns out having ui
connect to chrome for the ime driver is unnecessary as chrome already
does this. So, removing the code.

Mash was connecting to the chrome for the keyboard service. This is
also problematic for similar reasons, so removing it too. Filed bug
to have chrome register keyboard with mash.

BUG=664267,662157,664264,683192,683289
TEST=none
R=moshayedi@chromium.org
==========

[Hadi, 2017-01-20 20:42:52]

On 2017/01/20 20:31:10, sky wrote:
> On 2017/01/20 19:45:15, Hadi wrote:
> > Do we still require "service:catalog" in services/ui/manifest.json?
> 
> We do need catalog as services/ui/service.cc connects to catalog, but the
> category name was wrong. I fixed it.

lgtm

[sky, 2017-01-20 20:44:13]

The CQ bit was unchecked by sky@chromium.org

[sky, 2017-01-20 20:44:17]

The CQ bit was checked by sky@chromium.org

[commit-bot: I haz the power, 2017-01-20 20:44:57]

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-01-20 21:30:57]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1484945057607760,
"parent_rev": "e5a535bb5a2fc99a090f81bde71ed50e974efa60", "commit_rev":
"1340ff2da37b5fcd669e08842cea9223b325a873"}

[commit-bot: I haz the power, 2017-01-20 21:31:37]

Description was changed from

==========
mash: Makes mash and service:ui not establish outgoing connections

The ui service was connecting to chrome for the ime driver. As the ui
service is a singleton and chrome isn't, this triggered launching
another process of chrome, which we don't want. Turns out having ui
connect to chrome for the ime driver is unnecessary as chrome already
does this. So, removing the code.

Mash was connecting to the chrome for the keyboard service. This is
also problematic for similar reasons, so removing it too. Filed bug
to have chrome register keyboard with mash.

BUG=664267,662157,664264,683192,683289
TEST=none
R=moshayedi@chromium.org
==========

to

==========
mash: Makes mash and service:ui not establish outgoing connections

The ui service was connecting to chrome for the ime driver. As the ui
service is a singleton and chrome isn't, this triggered launching
another process of chrome, which we don't want. Turns out having ui
connect to chrome for the ime driver is unnecessary as chrome already
does this. So, removing the code.

Mash was connecting to the chrome for the keyboard service. This is
also problematic for similar reasons, so removing it too. Filed bug
to have chrome register keyboard with mash.

BUG=664267,662157,664264,683192,683289
TEST=none
R=moshayedi@chromium.org

Review-Url: https://codereview.chromium.org/2645683007
Cr-Commit-Position: refs/heads/master@{#445172}
Committed:
https://chromium.googlesource.com/chromium/src/+/1340ff2da37b5fcd669e08842cea...
==========

[commit-bot: I haz the power, 2017-01-20 21:31:38]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/1340ff2da37b5fcd669e08842cea...