Remove calls to MessageLoop::current() in mojo.

Remove calls to MessageLoop::current() in mojo.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=ben@chromium.org

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

[fdoray, 2016-06-21 17:20:11]

Can you review this CL? Thanks.

[Ben Goodger (Google), 2016-06-21 17:26:39]

lgtm

[fdoray, 2016-06-21 17:29:59]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2016-06-21 17:30:30]

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

[commit-bot: I haz the power, 2016-06-21 17:37:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-21 17:49:50]

Description was changed from

==========
Remove calls to MessageLoop::current() in mojo.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=ben@chromium.org
==========

to

==========
Remove calls to MessageLoop::current() in mojo.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=ben@chromium.org

Committed: https://crrev.com/b9d291f3d13f4691eb24ae93b4a23d091125e972
Cr-Commit-Position: refs/heads/master@{#401028}
==========

[commit-bot: I haz the power, 2016-06-21 17:49:51]

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