Autoplayed next video should also be PIP
source link: https://bugzilla.mozilla.org/show_bug.cgi?id=1611643
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Autoplayed next video should also be PIP
Categories
(Toolkit :: Picture-in-Picture, enhancement)
Tracking
(ASSIGNED bug found in Firefox 74 with no priority)
People
(Reporter: yoasif, Assigned: katkoor2)
References
(Blocks 2 open bugs)
Details
Seen this asked for on various places, but also experienced a desire for this myself.
- Start watching a series on Plex or Netflix
- Enter PIP
- Navigate to another app (like a game)
Once the next video starts playing (initiated by the website), PIP mode is disabled and the video continues playing in the original window. User has to move back to the Firefox tab and re-enable PIP.
It'd be nice if PIP were to recognize that a video started to play in the same tab that the original PIP video was being played from, and showed the new video in PIP as well.
¡Hola!
Just experienced this in Nightly and it is in fact a bit jarring.
Updating flags accordingly FWIW.
¡Gracias!
Alex
Udemy.com is also affected by this bug when viewing course videos.
By the way, is there a way to bump this? Because it's interfering with my workflow and I can't be the only one.
One idea to address this is to notice when PiP is shut down due to <video>
element removal, and to remember the coordinates of the removed <video>
... and then have a timer that checks to see if a new <video>
element exists at (roughly) the same coordinates, and if so, open that in PiP. That timer would probably need to be on the scale of seconds - say 1 or 2 to start.
This timer should be tied to the lifetime of the document, so if the page navigates away somehow, we should cancel the timer and throw it away.
So wait. Does this mean the fix is in the next version of Firefox?
(In reply to OpenMySourceCode from comment #8)
So wait. Does this mean the fix is in the next version of Firefox?
Patches are currently still in review. But if we can get it approved and merged soon (before December 2), then we can get that fix in for Nightly. :)
(However, not until much later for Firefox release)
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK