arc: Handle ARC events in MD Settings

chrome/browser/resources/settings/android_apps_page/android_apps_page.js

Index: chrome/browser/resources/settings/android_apps_page/android_apps_page.js
diff --git a/chrome/browser/resources/settings/android_apps_page/android_apps_page.js b/chrome/browser/resources/settings/android_apps_page/android_apps_page.js
index 861731780652ab51607d5907c609012ddb6e61da..baa88b61279c66dee9a39b666b0ff0f5982f50e1 100644
--- a/chrome/browser/resources/settings/android_apps_page/android_apps_page.js
+++ b/chrome/browser/resources/settings/android_apps_page/android_apps_page.js
@@ -55,6 +55,10 @@ Polymer({
    */
   androidAppsInfoUpdate_: function(info) {
     this.androidAppsInfo_ = info;
+    if (!this.androidAppsInfo_.playStoreEnabled) {
+      if (settings.getCurrentRoute() == settings.Route.ANDROID_APPS_DETAILS)

[stevenjb, 2017/05/10 16:47:03]

Combine these ifs.

[khmel, 2017/05/10 21:48:12]

Done.

+        settings.navigateTo(settings.Route.ANDROID_APPS);

[stevenjb, 2017/05/10 16:47:03]

nit: settings.navigateToPreviousRoute();

[khmel, 2017/05/10 21:48:12]

Done.
My concern was what if user directly opens ANDROID_APPS_DETAILS. IIUC this would
be possible to do by providing direct URL in settings.

[stevenjb, 2017/05/10 22:35:44]

In that case we would just return to the main Settings page, which is fine, but
in general using navigateToPreviousRoute() is a bit more robust.

+    }
   },
 
   /**
@@ -68,7 +72,7 @@ Polymer({
 
   /** @private */
   onSubpageTap_: function() {
-    if (this.androidAppsInfo_.appReady)
+    if (this.androidAppsInfo_.playStoreEnabled)
       settings.navigateTo(settings.Route.ANDROID_APPS_DETAILS);
   },
 });