On some site the videos don't resume after being paused when in Picture-in-Picture mode
Categories
(Toolkit :: Picture-in-Picture, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox74 | --- | fix-optional |
firefox75 | --- | affected |
People
(Reporter: obotisan, Assigned: asafko)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fidefe-MR1-2022])
Attachments
(1 file)
9.85 MB,
image/gif
|
Details |
Affected versions
- Firefox 74.0b2
- Firefox 75.0a1
Affected platforms
- Windows 10 x64
- macOS 10.13
- Ubuntu 18.04 x64
Steps to reproduce
- Go to Netflix and start a video.
- Click on the Picture-in-Picture button.
- Pause the video and click on the close button.
- Click on the play button.
Expected result
- The video plays without any issues.
Actual result
- The video is still paused.
Regression range
- This is not a regression. I can reproduce the issue on builds from 2019-09-09
Additional notes
- You have to click on play two times in order for the video resume.
- Please look at the attached gif.
- This issue is reproducing on Hulu and HBOGo, too. There might be other sites affected.
Comment 1•5 years ago
|
||
It looks like these site's players have their own internal play/pause state that's not being updated when the video is paused externally (by Firefox).
Hey astevenson, do you think we could reach out to our friends at Netflix about this? Would they be willing to add an event listener for the pause
and play
events to update the internal state of their players?
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Mike,
It's noted that this is affecting Hulu and HBOGo as well, we should contact them all I suppose.
Updated•3 years ago
|
Updated•3 years ago
|
As of FF 96.0.3 and Nightly 98, I can no longer reproduce the issue on HBO Max on macOS 11.6.
On Hulu, the issue is intermittent - Hulu player occasionally doesn't update the state of the play button.
On Netflix, however, the issue got worse - now it's impossible to resume playback after pausing it from PiP.
I reached out to the Netflix team about the issue, and will close this bug and keep track of the resolution in https://bugzilla.mozilla.org/show_bug.cgi?id=1752132
Description
•