onShowCustomView

android_webview/java/src/org/chromium/android_webview/AwContents.java

Index: android_webview/java/src/org/chromium/android_webview/AwContents.java
diff --git a/android_webview/java/src/org/chromium/android_webview/AwContents.java b/android_webview/java/src/org/chromium/android_webview/AwContents.java
index 64bf97d00542580c07b4aa1b902945486ee993c0..df8732c5299778910635b8770fb99f9f9844c609 100644
--- a/android_webview/java/src/org/chromium/android_webview/AwContents.java
+++ b/android_webview/java/src/org/chromium/android_webview/AwContents.java
@@ -25,6 +25,7 @@ import android.webkit.ValueCallback;
 import org.chromium.base.CalledByNative;
 import org.chromium.base.JNINamespace;
 import org.chromium.base.ThreadUtils;
+import org.chromium.content.browser.ContentVideoView;
 import org.chromium.content.browser.ContentViewCore;
 import org.chromium.content.browser.LoadUrlParams;
 import org.chromium.content.browser.NavigationHistory;
@@ -245,6 +246,9 @@ public class AwContents {
         mPossiblyStaleHitTestData = new HitTestData();
         nativeDidInitializeContentViewCore(mNativeAwContents,
                 mContentViewCore.getNativeContentViewCore());
+
+        ContentVideoView.registerContentVideoViewContextDelegate(
+                new AwContentVideoViewDelegate(contentsClient, containerView.getContext()));

[joth, 2012/12/08 00:17:58]

There's one AwContents per WebView, and many can exist at once, so creating a
new singleton AwContentVideoViewDelegate instance per webview wired up to the
most-recently-created webview is not going to work.

Unless we can update ContentVideoView to support one delegate per
ContentViewCore, I think we'll need to keep a map of weak references so we can
find the correct AwContentClient instance for a given onShowCustomView call (for
a given ContentViewCore originating the full screen request)

[acleung, 2013/01/07 23:40:03]

Ya. I don't even know what happens if there are multiple fullscreen video on
different webview host. In theory, if one goes full screen after the other, it
should take over the existing one.

I think I will open a sperate issue to track the problem of multiple fullscreen
custom views which might require further restructure of content video view.

     }
 
     public ContentViewCore getContentViewCore() {