Closed
Bug 2055069
Opened 3 months ago
Closed 1 month ago
YouTube playback speed UI doesn't match rate value set from PiP player
Categories
(Toolkit :: Picture-in-Picture, defect, P3)
Toolkit
Picture-in-Picture
Tracking
()
VERIFIED
FIXED
158 Branch
People
(Reporter: kpatenio, Assigned: kpatenio)
References
Details
(Whiteboard: [fidefe-post-nova])
Attachments
(1 external file)
Note: this is a follow up to Bug 1875517. This issue was caught while reviewing the patch for that ticket.
STR:
- Ensure playback speed control pref (
media.videocontrols.picture-in-picture.playback-speed.enabled) is enabled once landed - Go to a youtube video
- Enable PiP
- Set playback speed on the PiP player
Expected: the youtube playback speed UI should match the rate selected in the PiP player
Actual: the speed is updated for the youtube video, but the UI does not match the set value
One possible fix is to add setPlaybackRate and getPlaybackRate overrides for our youtube wrapper. Currently, we try to get a reference to the youtube player to adjust the video volume and mute state. We can probably use the same approach to read and write the video's playback rate.
Updated•2 months ago
|
Pushed by kpatenio@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/fcdcb216e7fc
https://hg.mozilla.org/integration/autoland/rev/98dace0994b8
sync youtube and pip playback rate settings. r=mconley
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
status-firefox158:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 158 Branch
Updated•1 month ago
|
QA Whiteboard: [qa-triage-done-c159/b158] [qa-ver-needed-c159/b158]
Flags: qe-verify+
Updated•27 days ago
|
QA Contact: oardelean
Reproducible on a 2026-09-10 Firefox Nightly build on Windows 11.
Verified as fixed on Firefox Nightly 159.0a1 and Firefox 158.0b1 on Windows 11, Ubuntu 22, macOS 13.
Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triage-done-c159/b158] [qa-ver-needed-c159/b158] → [qa-triage-done-c159/b158] [qa-ver-done-c159/b158]
status-firefox159:
--- → verified
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•