Open Bug 1562218 Opened 4 months ago Updated 4 days ago

[Intermittent] PiP window displays only a white border instead of a video

Categories

(Toolkit :: Video/Audio Controls, defect, P2)

All
Windows 10
defect

Tracking

()

Tracking Status
firefox67 --- disabled
firefox68 --- disabled
firefox69 --- affected
firefox70 --- affected
firefox71 --- affected

People

(Reporter: tbabos, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Attached image 2019-06-27_14h24_37.png

Affected versions
Nightly 69.0a1 (2019-06-27) (64-bit)

Affected platforms
Windows 10 x64

Steps to reproduce
have 2 monitors

  • Launch Firefox
  • Go to any page with video content, such as Youtube
  • Move the Firefox window on the second monitor
  • Open anything on the main monitor, such as a different browser or etc.
  • Toggle PiP for the video

Expected Result:
PiP is correctly displayed for the video

Actual Result:
Very Intermittent: there will be only a white border displayed on the main monitor where the PiP window should be. Check attached screenshot.

  • The sound of the video is played back and the controls are working but not visible.
Duplicate of this bug: 1578423
Attached image Nightly71

Screenshot in Nightly71

Reproduced on latest Nightly 71.0a1 (2019-09-16) (64-bit) on Windows 10 x64 on the first PiP toggle click. Investigating steps to repro, still very intermittent.

Just making sure you're aware of this one, astevenson.

I got into this state, and then I resized the player window, and then noticed the video playing in the top left corner! (The resized window doesn't draw correctly - the transparent white rectangle in the corner was what the window looked like before I resized it - it didn't redraw after the resize was complete).

I can reproduce this often enough, and it's a disappointing enough result, that I'm upgrading its importance.

Priority: P3 → P2

Change the status for beta to have the same as nightly and release.
For more information, please visit auto_nag documentation.

Barret is able to reproduce this quite often, and has done so a few days in a row, so cc'ing. Also cc'ing mstange who helped poke at Barret's machine while in the broken state.

Hey sotaro, mstange suggested you as someone who might have a sense of what's going wrong here. Specifically, the screenshot in comment 5 got mstange's attention: the video frames are scaled to the right size, but their position is offset as if the window (before resizing) was originally at (0,0), and then the rectangle where the video becomes visible is the intersection between the actual window and the window had it been at (0,0) before resizing.

We also noticed that this bug also occurs for the chrome of the window that Gecko draws in the parent process (we confirmed this by adding a border around the remote <browser> which renders in the parent process).

Is it possible that the compositor is confused about where the window is that it's supposed to be rendering into? Do you have any ideas of what we could do to debug this?

Flags: needinfo?(sotaro.ikeda.g)

We also noticed that this bug also occurs for the chrome of the window that Gecko draws in the parent process (we confirmed this by adding a border around the remote <browser> which renders in the parent process).

:mconley, can you explain more about it?

Is it possible that the compositor is confused about where the window is that it's supposed to be rendering into? Do you have any ideas of what we could do to debug this?

If layout provides wrong information, it could happen.

Flags: needinfo?(mconley)
Flags: needinfo?(mconley)
See Also: → 1573710

I believe Gankra has been tackling a related issue in bug 1573710, so hopefully when that's sorted out, this one will get sorted at the same time.

Flags: needinfo?(sotaro.ikeda.g)
You need to log in before you can comment on or make changes to this bug.