Hmm, this sounds like issue 866323 on YouTube TV -- but that currently looks like a page level issue. What site are you seeing this on? Does it happen on this test video:

http://storage.googleapis.com/dalecurtis/buck720.mp4

+liberato

This video has been tested and the same problem will still occur.

by "covered by black", do you mean that part of the video is covered by black, or all of it?  if part, which part (top, bottom, etc.)?

when you start devtools, with the video playing, does it return to normal?

> The page I saw in dev_tools is in landscape mode.

I have no idea about how that happens.

As per comment#4 adding Needs=FB label. 

@409694076@gg: Please provide screencast as well, this would help in further triaging.

Thanks!

The black part is below the status bar and has the same width as the width of the screen.
The video is displayed below the black part and can be played normally, but operations such as pauses cannot be performed.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is the screencast about this questions

Deleted: 115BAB96-FBA9-468B-A872-EBFB61EF6AC7.png 2.5 MB

	115BAB96-FBA9-468B-A872-EBFB61EF6AC7.png 2.5 MB View Download

Deleted: 845CE219-0EDF-4127-A112-6056014C3A83.png 1.4 MB

	845CE219-0EDF-4127-A112-6056014C3A83.png 1.4 MB View Download

Tested the issue on android and unable to reproduce this issue

Steps to reproduce:
--------------------------
1. Launched chrome and navigated to http://storage.googleapis.com/dalecurtis/buck720.mp4
2. Entered fullscreen and exit fullscreen and not seeing black areas as shown in screenshot.

Chrome version:
69.0.3497.100
OS:
Android 7.0 

Android device:
Samsung s7  

@409694076: Could you please let us know the device details on which this issue is seen. Any further info on reproducing would help in further triaging.

Thanks!

thanks for providing the screen shots in c#8.

can you interact with the upper omnibox?  the lower omnibox?  probably at most one is real.

i'm starting to suspect that this isn't a media issue directly, but rather something going on in the browser during the transition.  if the browser is getting the wrong idea about where the CompositorView is, then all sorts of things might go wrong with video.

First, the Auto-rotate of the phone is to be turned on.
Android device:HUAWEI mate9 && Android 5.0
Android device:OPPO R15 && Android 7.0
There are such problems on both models.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The Example for the question
device：Galaxy s8
Android version：8.0.0

Deleted: 27F6BB2A-18B0-48F6-8AE2-732E9B44E5E5.png 1.3 MB

	27F6BB2A-18B0-48F6-8AE2-732E9B44E5E5.png 1.3 MB View Download

Deleted: A6C680B4-88F3-42A9-914C-7B76288C0EFC.MOV 1014 KB

	A6C680B4-88F3-42A9-914C-7B76288C0EFC.MOV 1014 KB View Download

When I use kUsingTextureOwner, the above problem will not appear. Why?

void AndroidVideoSurfaceChooserImpl::Choose() {

	...
	
	new_overlay_state = kUsingTextureOwner;
	
	// Make sure that we're in |new_overlay_state_|.
	if (new_overlay_state == kUsingTextureOwner)
		SwitchToTextureOwner();
	else
		SwitchToOverlay(needs_power_efficient);

}

Chrome handles composition of the SurfaceTexture, where as the SurfaceView is a whole different layer. It's possible we're not updating it's position correctly (hopefully) or worse the OS layer is messing up the position :|

Using ST instead of SV will cause >10% power regression, so we use SV for fullscreen.

what's particularly strange about this is that the entire page is offset, not just the video.

that points to something going wrong with (a) the position of the chrome compositor's surface on the display, or (b) chrome's calculation of how much padding to leave at the top  when drawing.  in other words, either the surface is moved, or chrome is drawing everything on the surface lower than it should.

when we enter / exit overlay mode, we do reconstruct the compositor output surface to turn on / off transparency support.

i have an s8 at my desk.  i'll try to repro.

ah -- the one screen shot shows two omniboxes.  that looks like the surface is probably positioned correctly, but chrome is drawing on it too low.

i've not been able to repro this so far in canary on my s8+.  will keep trying.

@4095: i have an s8+ with 8.0.0, and auto-rotate, and i can't get this to happen.

what URL are you using?

i'm using https://storage.googleapis.com/watk/v then select an mp4 video.

thanks!