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

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

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/76388ee0f590195676606308a2666dd25ae5b4b7
Cr-Commit-Position: refs/heads/master@{#403228}

[fdoray, 2016-06-29 17:29:49]

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

[fdoray, 2016-06-29 17:29:50]

Can you review this CL? Thanks.

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

lgtm

[fdoray, 2016-06-30 17:24:18]

The CQ bit was checked by fdoray@chromium.org

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

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-30 18:29:15]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-30 18:29:33]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-06-30 18:30:47]

Description was changed from

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

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 content.

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/76388ee0f590195676606308a2666dd25ae5b4b7
Cr-Commit-Position: refs/heads/master@{#403228}
==========

[commit-bot: I haz the power, 2016-06-30 18:30:49]

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

[kelvinp, 2016-06-30 20:24:32]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2116643002/ by kelvinp@chromium.org.

The reason for reverting is: Failed Browser tests and webkit tests.

Browser tests failed:
DevToolsSanityTest.AutoAttachToWindowOpen
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests%20%28dbg%2...

webkit tests failed:
inspector/sources/debugger-pause/debugger-pause-on-promise-rejection.html
inspector/sources/debugger/live-edit-no-reveal.html
inspector/sources/debugger-step/debugger-step-out-document-write.html
inspector/sources/debugger-step/debugger-step-over-inlined-scripts.html
inspector/sources/debugger-console/debug-console-command.html
inspector/sources/debugger-frameworks/frameworks-sourcemap.html
inspector-protocol/debugger/debugger-doesnt-step-into-injected-script.html
inspector/sources/debugger-step/debugger-step-over-document-write.html
inspector/sources/debugger-step/debugger-step-out-event-listener.html
inspector/sources/debugger-console/debugger-command-line-api.html
inspector/sources/debugger-step/debugger-step-into-event-listener.html
inspector/sources/debugger-breakpoints/dom-breakpoints.html
inspector/sources/debugger/debugger-return-value.html
inspector/sources/debugger-ui/debugger-inline-values.html
inspector/sources/debugger-ui/reveal-not-skipped.html
inspector-protocol/debugger/stepping-with-blackboxed-ranges.html
inspector/sources/debugger-step/debugger-step-in.html
inspector/sources/debugger-frameworks/frameworks-skip-step-in.html
inspector/sources/debugger-step/debugger-step-into-across-timeouts.html
inspector/sources/debugger-frameworks/frameworks-step-from-framework.html
inspector/sources/debugger-step/debugger-step-into-custom-element-callbacks.html
inspector/sources/debugger-pause/debugger-eval-while-paused-throws.html
inspector/sources/debugger/mutation-observer-suspend-while-paused.html
inspector/sources/debugger-frameworks/frameworks-dom-xhr-event-breakpoints.html
inspector-protocol/debugger/postMessage-on-pause.html
inspector/sources/debugger-frameworks/frameworks-step-into-skips-setTimeout.html
inspector/sources/debugger/live-edit.html
inspector/sources/debugger-frameworks/frameworks-steppings.html
inspector-protocol/debugger/continueToLocation.html
inspector/sources/debugger-pause/debugger-eval-on-call-frame-inside-iframe.html
inspector/sources/debugger-step/debugger-step-into-document-write.html
inspector-protocol/debugger/updateCallFrameScopes.html
inspector/sources/debugger-step/debugger-step-over.html
inspector/sources/debugger-frameworks/frameworks-jquery.html
inspector-protocol/debugger/debugger-setBlackboxPatterns.html
inspector/sources/debugger-step/debugger-step-into-inlined-scripts.html
inspector/sources/debugger-step/debugger-step-over-across-timeouts.html
inspector/sources/debugger-step/debugger-step-through-promises.html
inspector/sources/debugger-step/debugger-step-out-custom-element-callbacks.html
inspector-protocol/debugger/step-over-caught-exception.html

https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11/build....