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

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

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
Committed: https://crrev.com/c16c6f870e4c1546b1e5e93205caa59d5c33e513
Cr-Commit-Position: refs/heads/master@{#402816}

[fdoray, 2016-06-28 20:26:06]

Description was changed from

==========
refactor chrome
==========

to

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

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
==========

[fdoray, 2016-06-28 20:26:06]

fdoray@chromium.org changed reviewers:
+ jochen@chromium.org

[fdoray, 2016-06-28 20:26:24]

Can you review this CL? Thanks.

[jochen (gone - plz use gerrit), 2016-06-29 15:17:56]

lgtm

[fdoray, 2016-06-29 15:18:30]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2016-06-29 15:19:24]

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-06-29 15:27:51]

Description was changed from

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

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
==========

to

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

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
==========

[commit-bot: I haz the power, 2016-06-29 15:27:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-29 15:28:02]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-06-29 15:29:17]

Description was changed from

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

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
==========

to

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

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

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

[commit-bot: I haz the power, 2016-06-29 15:29:22]

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