Fix: long-tapping a WebAPK in recents shows Chrome.

chrome/android/java/AndroidManifest.xml

Index: chrome/android/java/AndroidManifest.xml
diff --git a/chrome/android/java/AndroidManifest.xml b/chrome/android/java/AndroidManifest.xml
index 7c67865ce4e2fbda87d2045d6b9e22a2b686fcc3..82dd0a89cf1cf79fd61e35eaeccc6ebf5f922252 100644
--- a/chrome/android/java/AndroidManifest.xml
+++ b/chrome/android/java/AndroidManifest.xml
@@ -564,7 +564,6 @@ by a child template that "extends" this file.
             android:theme="@style/WebappTheme"
             android:label="@string/webapp_activity_title"
             android:launchMode="singleTop"
-            android:documentLaunchMode="intoExisting"
             android:windowSoftInputMode="adjustResize"
             android:persistableMode="persistNever"
             android:hardwareAccelerated="false"
@@ -576,7 +575,7 @@ by a child template that "extends" this file.
             android:theme="@style/WebappTheme"
             android:icon="@mipmap/app_shortcut_icon"
             android:label="@string/webapp_activity_title"
-            android:launchMode="singleTask"
+            android:launchMode="singleTop"

[Ted C, 2017/03/23 23:16:07]

The assigner pretty strongly assumes a 1:1 relationship, and this breaks that in
all types of ways.  This has to remain singleTask if you want the existing logic
to work.

[Xi Han, 2017/03/24 16:05:36]

I think only a WebAPK will launch a WebApkAcitivity instance, and each WebAPK
will have its own WebApkAcitvity since the meta-date in the Intent to start the
activity is unique for each WebAPK. Beside, we have a launcher class
WebappLauncherActivity to launch the WebApkActivityXXX, the activity launching
order is:
 WebAPK's main activity -> WebappLauncherActivity -> WebApkActivityXXX (has a
suffix number on KK)

Do you think it will really break by changing to singleTop ? 

             android:windowSoftInputMode="adjustResize"
             android:persistableMode="persistNever"
             android:hardwareAccelerated="false"