Public glue layer plumbing for View#startActivityForResult

android_webview/java/src/org/chromium/android_webview/FullScreenView.java

Index: android_webview/java/src/org/chromium/android_webview/FullScreenView.java
diff --git a/android_webview/java/src/org/chromium/android_webview/FullScreenView.java b/android_webview/java/src/org/chromium/android_webview/FullScreenView.java
index 1eb96a4eda3dd97c99e511031b4607bcfac1b2dd..322167f806315f1cb3a25368c2a8e697213a7092 100644
--- a/android_webview/java/src/org/chromium/android_webview/FullScreenView.java
+++ b/android_webview/java/src/org/chromium/android_webview/FullScreenView.java
@@ -5,6 +5,7 @@
 package org.chromium.android_webview;
 
 import android.content.Context;
+import android.content.Intent;
 import android.content.res.Configuration;
 import android.graphics.Canvas;
 import android.graphics.Paint;
@@ -230,6 +231,11 @@ public class FullScreenView extends FrameLayout {
         }
 
         @Override
+        public void super_startActivityForResult(Intent intent, int requestCode) {
+            // Intentional no-op

[hush (inactive), 2015/10/14 01:21:32]

We need to support this on FullScreenView, because a dom element can go to
fullscreen mode by calling JS API requestFullscreen().

In order to send intents from a FullScreenView(which is a FrameLayout), I think
we can pass AwContents into the constructor of FullScreenView and use AwContents
to send the intent.

But this will probably be done in a separate CL.

[sgurun-gerrit only, 2015/10/14 17:40:13]

Full screen view constructor already receives an AwContents, missed?

public FullScreenView(Context context, AwViewMethods awViewMethods,
            AwContents awContents) {
        super(context);
        setAwViewMethods(awViewMethods);
        mAwContents = awContents;
        mInternalAccessAdapter = new InternalAccessAdapter();
    }

[hush (inactive), 2015/10/14 21:33:59]

So the goal here is to support "text processing" feature in fullscreen mode by
firing the intents through the WebView object, instead of the framelayout
object.
In order to achieve this, I think AwContents#startActivityForResult should call
super_startActivityForResult on the initial InternalAccessDelegate (that is
WebViewChromium). 

+        }
+
+        @Override
         public boolean awakenScrollBars() {
             return FullScreenView.this.awakenScrollBars(0);
         }