Android: Never automatically enter fullscreen when media playback starts.

content/browser/media/android/browser_media_player_manager.h

Index: content/browser/media/android/browser_media_player_manager.h
diff --git a/content/browser/media/android/browser_media_player_manager.h b/content/browser/media/android/browser_media_player_manager.h
index 05040a15fb9793907162382f00bafbbbcbd6d404..044cced8d354f3dd795fd0319cb898c87ebcd933 100644
--- a/content/browser/media/android/browser_media_player_manager.h
+++ b/content/browser/media/android/browser_media_player_manager.h
@@ -97,8 +97,6 @@ class CONTENT_EXPORT BrowserMediaPlayerManager
   media::MediaPlayerAndroid* GetPlayer(int player_id) override;
   void RequestFullScreen(int player_id) override;
 #if defined(VIDEO_HOLE)
-  bool ShouldUseVideoOverlayForEmbeddedEncryptedVideo() override;

[xhwang, 2015/03/20 18:07:44]

How about the renderer side? e.g.

https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/m...

https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/m...

[ddorwin, 2015/03/20 18:45:25]

This appears to be related to getting a surface. Fullscreen is mentioned there,
but it's not clear that the reason is related to this.

qinmin@?

[qinmin, 2015/03/20 19:47:46]

This surface is for hole punching and probably we don't want to remove it. TV
uses this to show L1 video for non-fullscreen mode

On 2015/03/20 18:45:25, ddorwin wrote:

[qinmin, 2015/03/20 20:31:49]

To be clear, browser side call is only used to request fullscreen, so we can
remove it here.
Renderer side call is needed by WebMediaPlayerAndroid to attach the hole
punching surface to the player, so we should keep the call.

-
   void AttachExternalVideoSurface(int player_id, jobject surface);
   void DetachExternalVideoSurface(int player_id);
   void OnFrameInfoUpdated();