New issue
Advanced search Search tips

Issue 883630 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Video display exception

Reported by 409694...@qq.com, Sep 13

Issue description

Example URL:

Steps to reproduce the problem:
1. Video plays normally in full screen, 
2. Pause
3. Press HOME button.
4. Open the browser again.

What is the expected behavior?
Video exits full screen
Video shows the last frame.

What went wrong?
Video exits full screen, video has no video content, only black.

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? N/A

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 7.0
Flash Version: 

Contents of chrome://gpu: 

When I debug in DevTools, the above situation does not occur, why?
 
Cc: liber...@chromium.org
We switch to SurfaceView when you go fullscreen to save quite a lot of power, but when switching back to inline if the video is paused, we can't get the last frame back from the SurfaceView, so you end up with black. Pressing play should start playback just fine though.

DevTools forces us to always use SurfaceTexture so the issue doesn't show up.

If you exit fullscreen while without using the home button we do try to spool the next frame so you don't end up with black, but in this case the home state transition loses too much state for us to know if spooling for the frame is a good idea or not. So I think this is WontFix. +liberato in case I'm off here.
Status: WontFix (was: Unconfirmed)
+1, though i'd modify the "without using the home button" part slightly.  we don't switch to a SurfaceTexture-backed frame immediately in that case, either.  We just keep using the overlay, possibly for a few more frames if they've already been decoded while we were in fullscreen.  The first frame to be decoded after the switch to inline with transition back to SurfaceTexture.

either way, i agree that this is WontFix, unfortunately.  by the time one presses pause, it's too late for chrome to change its mind about using a SurfaceView or not.
thank you for your reply.
Is there an optimized solution for this problem?

Sign in to add a comment