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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

BUG=616447
Committed: https://crrev.com/e94d86444553f5bf3abe0af715fa6f49acc18f67
Cr-Commit-Position: refs/heads/master@{#404207}

[fdoray, 2016-07-05 17:26:42]

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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

BUG=616447
==========

[fdoray, 2016-07-05 18:28:11]

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

[fdoray, 2016-07-05 18:28:12]

Can you review this CL?

It is identical to a CL that you already reviewed, except for a fix in
content/renderer/devtools/devtools_agent.cc to avoid breaking webkit unit tests.

[jochen (gone - plz use gerrit), 2016-07-06 11:24:52]

https://codereview.chromium.org/2123653003/diff/40001/content/renderer/devtoo...
File content/renderer/devtools/devtools_agent.cc (right):

https://codereview.chromium.org/2123653003/diff/40001/content/renderer/devtoo...
content/renderer/devtools/devtools_agent.cc:51: WebKitClientMessageLoopImpl() {
DCHECK(CalledOnValidThread()); }
how would you ever be able to call the constructor on an invalid thread?

[fdoray, 2016-07-06 14:29:08]

PTAnL

https://codereview.chromium.org/2123653003/diff/40001/content/renderer/devtoo...
File content/renderer/devtools/devtools_agent.cc (right):

https://codereview.chromium.org/2123653003/diff/40001/content/renderer/devtoo...
content/renderer/devtools/devtools_agent.cc:51: WebKitClientMessageLoopImpl() {
DCHECK(CalledOnValidThread()); }
On 2016/07/06 11:24:52, jochen wrote:
> how would you ever be able to call the constructor on an invalid thread?

Done.

[jochen (gone - plz use gerrit), 2016-07-07 08:59:18]

lgtm

[fdoray, 2016-07-07 13:52:30]

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

[fdoray, 2016-07-07 13:52:30]

scottmg@chromium.org: Can you take a look at device/gamepad/gamepad_provider.cc?
jochen@ already reviewed this file when it was in content/ yesterday.

[fdoray, 2016-07-07 13:53:46]

fdoray@chromium.org changed reviewers:
+ bajones@chromium.org
- scottmg@chromium.org

[fdoray, 2016-07-07 13:53:46]

bajones@: Can you review device/gamepad/gamepad_provider.cc? jochen@ already
reviewed it before it was moved from content/ to device/.

[bajones, 2016-07-07 15:35:03]

On 2016/07/07 13:53:46, fdoray wrote:
> bajones@: Can you review device/gamepad/gamepad_provider.cc? jochen@ already
> reviewed it before it was moved from content/ to device/.

device/gamepad/ LGTM. Sorry for moving files out from under you. :)

[fdoray, 2016-07-07 15:41:32]

The CQ bit was checked by fdoray@chromium.org

[fdoray, 2016-07-07 15:41:33]

The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org
Link to the patchset: https://codereview.chromium.org/2123653003/#ps80001
(title: "rebase")

[commit-bot: I haz the power, 2016-07-07 15:42:12]

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-07-07 19:19:14]

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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

BUG=616447
==========

[commit-bot: I haz the power, 2016-07-07 19:19:15]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-07-07 19:21:44]

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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

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.

This CL is identical to https://codereview.chromium.org/2105173004/
except for a fix to content/renderer/devtools/devtools_agent.cc

BUG=616447

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

[commit-bot: I haz the power, 2016-07-07 19:21:45]

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