Chromium Code Reviews (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out

Unified Diff: content/browser/gamepad/

Issue 133943002: Gamepad API support for chrome on android (Closed) Base URL:
Patch Set: Created 6 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/browser/gamepad/
diff --git a/content/browser/gamepad/ b/content/browser/gamepad/
index 1cc7aab73f5daba2e6984c3e626275c27fbf06b8..430940b4bf3d97884e7876b53e8962e3da0a1aa7 100644
--- a/content/browser/gamepad/
+++ b/content/browser/gamepad/
@@ -117,6 +117,10 @@ void GamepadProvider::Initialize(scoped_ptr<GamepadDataFetcher> fetcher) {
// On Linux, the data fetcher needs to watch file descriptors, so the message
// loop needs to be a libevent loop.
const base::MessageLoop::Type kMessageLoopType = base::MessageLoop::TYPE_IO;
+#elif defined(OS_ANDROID)
+ // On Android, keeping a message loop of default type.
+ const base::MessageLoop::Type kMessageLoopType =
+ base::MessageLoop::TYPE_DEFAULT;
// On Mac, the data fetcher uses IOKit which depends on CFRunLoop, so the
// message loop needs to be a UI-type loop. On Windows it must be a UI loop

Powered by Google App Engine
This is Rietveld 408576698