| commit | e94d86444553f5bf3abe0af715fa6f49acc18f67 | [log] [tgz] |
|---|---|---|
| author | fdoray <[email protected]> | Thu Jul 07 19:19:01 2016 |
| committer | Commit bot <[email protected]> | Thu Jul 07 19:21:32 2016 |
| tree | 96317783c18794f12b693540a1399f9803eb47cb | |
| parent | b0531d0c52a82a5afd38cdc7d2cea05a1aa2f39c [diff] |
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 Review-Url: https://codereview.chromium.org/2123653003 Cr-Commit-Position: refs/heads/master@{#404207}