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

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

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=jam@chromium.org

Committed: https://crrev.com/9b57365e023ea624c1441ab822319c183bb4bffc
Cr-Commit-Position: refs/heads/master@{#401384}

[fdoray, 2016-06-22 18:53:50]

Can you review this CL? Thanks.

[jam, 2016-06-22 19:35:39]

lgtm

[fdoray, 2016-06-22 19:49:14]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2016-06-22 19:50:06]

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

[commit-bot: I haz the power, 2016-06-22 19:55:50]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-06-22 19:57:37]

Description was changed from

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

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=jam@chromium.org
==========

to

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

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=jam@chromium.org

Committed: https://crrev.com/9b57365e023ea624c1441ab822319c183bb4bffc
Cr-Commit-Position: refs/heads/master@{#401384}
==========

[commit-bot: I haz the power, 2016-06-22 19:57:38]

Patchset 2 (id:??) landed as
https://crrev.com/9b57365e023ea624c1441ab822319c183bb4bffc
Cr-Commit-Position: refs/heads/master@{#401384}