Per-CL bisect information:
Good commit:589184
Bad commit:589185

Suspect CL:
https://chromium.googlesource.com/chromium/src/+/62898a131761fbeeac3f2b2f7c2c0512f7ca14a9

dtapuska@  Might be it looks like this issue is related to your change. please look into once, if its not related to your change please reassign back to me. 

Thanks!

Please find the log and Video @ http://go/chrome-androidlogs1/8/893453

Bo you do have any experience with this WWE app? It appears that they are using multiple webviews here and not actually entering fullscreen at all. The app is trapping the prefixed fullscreen app and resizing the webview that has the video and rotating it. But when the unprefixed version is enabled then the jwplayer code they are using is trapping into requesting fullscreen from the document and it isn't hitting their overloaded code themselves.

I don't think there is anything wrong here in the web platform and is just due to their problematic code.

Specifically inside the APK there is a file called mobile_workarounds.js

It contains this text:

// This file contains workarounds for running JW Player in a WebView on Android

// Null out fullscreen functions - these are used by the webplayer to determine whether it should do fullscreen handling via DOM or via provider.setFullscreen()
// We want to use provider.setFullscreen() because on Android < 4.4 the DOM fullscreen functions are not available and we want to have a consistent 
// implementation for all versions
document.webkitExitFullscreen = null;
document.webkitCancelFullScreen = null;

If "document.exitFullscreen = null" is added to this list it should work correctly

Closing as this is an app issue.