apmanager: post tasks to task runners, not message loops
Message loops no longer support being task receivers directly
in the new libcrhome.
BUG=b:37434548
TEST=unit tests
Change-Id: Id77fe6302a6ae7bab44e05a7990ba7bcddb28311
Reviewed-on: https://chromium-review.googlesource.com/1070540
Commit-Ready: Eric Caruso <[email protected]>
Tested-by: Eric Caruso <[email protected]>
Reviewed-by: Dan Erat <[email protected]>
diff --git a/event_dispatcher.cc b/event_dispatcher.cc
index 5e7d831..cb7f673 100644
--- a/event_dispatcher.cc
+++ b/event_dispatcher.cc
@@ -39,7 +39,7 @@
bool EventDispatcher::PostTask(const base::Closure& task) {
if (!base::MessageLoop::current())
return false;
- base::MessageLoop::current()->PostTask(FROM_HERE, task);
+ base::MessageLoop::current()->task_runner()->PostTask(FROM_HERE, task);
return true;
}
@@ -47,7 +47,7 @@
int64_t delay_ms) {
if (!base::MessageLoop::current())
return false;
- base::MessageLoop::current()->PostDelayedTask(
+ base::MessageLoop::current()->task_runner()->PostDelayedTask(
FROM_HERE, task, base::TimeDelta::FromMilliseconds(delay_ms));
return true;
}
