Suggestion: Add speed button for Youtube in picture-in-picture(PiP) modals
Categories
(Toolkit :: Picture-in-Picture, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: wtds.trabalho, Assigned: simon.rosen17)
References
(Blocks 3 open bugs)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0
Steps to reproduce:
- Play youtube video: https://www.youtube.com/watch?v=Q8xawBknV4s
- Open PiP modal
- Can't change video speed from PiP Modal
Actual results:
I can't change Youtube video speed from PiP modals
Expected results:
Suggestions: Add ways to control video playing speed in PiP modals
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Picture-in-Picture' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Assignee | ||
Comment 2•2 months ago
|
||
Adds a playback speed button (shown with the improved video controls) to
the Picture-in-Picture window. It opens a panel, modeled on the existing
subtitles settings panel, containing a live rate readout, a 0.25x-2x
slider, and one-tap presets for 0.5x/1x/1.5x/2x. The < and > keys step
through the standard presets.
The rate is applied to the originating video through new overridable
PictureInPictureChildVideoWrapper methods (getPlaybackRate/setPlaybackRate)
with the usual fallback implementation. A ratechange listener on the
originating video keeps the panel in sync when the rate is changed from
the page, and the originating video's rate is carried into the PiP window
when it opens (mirroring the existing volume flow).
Developed with AI assistance (Claude Code) under my direction; reviewed
and tested locally (browser_playbackRate.js) before submitting.
Updated•2 months ago
|
Comment 5•1 month ago
|
||
Revert for causing bc failures on browser_playbackRate.js.
Comment 7•1 month ago
|
||
| bugherder | ||
| Assignee | ||
Comment 8•1 month ago
|
||
Re-landed as 1ee9c0836cf6 (merged to central in comment 7).
The browser_playbackRate.js failure was a test bug, not a product bug: the
playback speed button is display:none below 640x360, and the test never sized
the PiP window, so the synthesized click landed on a hidden button. The test
now resizes, waits for the button to actually be visible, and retries the
click. kpatenio's try push came back green across Linux and Windows
test-verify before re-landing.
Sorry for the delay clearing this.
Updated•25 days ago
|
Description
•