Workaround for Samsung email issues

android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java

Index: android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java
diff --git a/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java b/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java
index 66779333e88e2b0175f4f0dcb441510308e16486..67a7ff80445ff0dd4d7d6781e46ae55d27c3b719 100644
--- a/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java
+++ b/android_webview/glue/java/src/com/android/webview/chromium/WebViewChromium.java
@@ -174,11 +174,16 @@ class WebViewChromium implements WebViewProvider, WebViewProvider.ScrollDelegate
         final boolean allowGeolocationOnInsecureOrigins =
                 mAppTargetSdkVersion <= Build.VERSION_CODES.M;
 
+        final String samsungEmailPackageId = "com.samsung.android.email.provider";

[aelias_OOO_until_Jul13, 2017/03/31 23:40:21]

I don't think an APK name check is called for here.  Name-checks can cause
mysterious problems (e.g. beta channel or derivative fork behaving different
from main one) so I think they're only appropriate for particularly unsafe/crazy
hacks.  Since this is just restoring the previous behavior that we shipped
before, I think it's cleaner to make it global all WebView with low enough
targetSdkVersion.  We can see that as a slower, safer way of rolling out this
breaking change.

[Changwan Ryu, 2017/04/01 00:07:56]

Done. Also checking with Samsung about the package name variants.

+        final boolean doNotUpdateSelectionOnMutatingSelectionRange =
+                samsungEmailPackageId.equals(mContext.getPackageName())
+                && mAppTargetSdkVersion <= Build.VERSION_CODES.M;

[aelias_OOO_until_Jul13, 2017/03/31 23:25:41]

Why M and below?  I would've expected N and below.  Some Samsung devices have
already shipped N (some variants of Galaxy S7), have you checked this issue does
not repro on them?

[Changwan Ryu, 2017/03/31 23:28:10]

Sorry I wasn't super clear about this. Samsung's initial test result indicates
that this does not happen on Android N. But I'll confirm with them.

[aelias_OOO_until_Jul13, 2017/03/31 23:40:21]

OK sounds good.  Targeting M is somewhat better if we can get away with it.

+
         mContentsClientAdapter = mFactory.createWebViewContentsClientAdapter(mWebView, mContext);
-        mWebSettings = new ContentSettingsAdapter(
-                new AwSettings(mContext, isAccessFromFileURLsGrantedByDefault,
-                        areLegacyQuirksEnabled, allowEmptyDocumentPersistence,
-                        allowGeolocationOnInsecureOrigins));
+        mWebSettings = new ContentSettingsAdapter(new AwSettings(mContext,
+                isAccessFromFileURLsGrantedByDefault, areLegacyQuirksEnabled,
+                allowEmptyDocumentPersistence, allowGeolocationOnInsecureOrigins,
+                doNotUpdateSelectionOnMutatingSelectionRange));
 
         if (mAppTargetSdkVersion < Build.VERSION_CODES.LOLLIPOP) {
             // Prior to Lollipop we always allowed third party cookies and mixed content.