Closed
Bug 1739151
Opened 3 years ago
Closed 4 months ago
Progress bar inside the “Now Playing” info panel doesn't reflect the state of an ongoing played video
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
VERIFIED
FIXED
133 Branch
People
(Reporter: asoncutean, Assigned: nerixdev)
References
Details
Attachments
(1 file, 1 obsolete file)
1.22 MB,
image/png
|
Details |
Affected versions
- 96.0a1 (2021-11-03)
- 95.0b2
- 94.0
Affected platforms
- macOS 11.0/12.0
Steps to reproduce
- Launch Firefox
- Access Youtube and play any video
- Click on the Play button from menu bar on the top right corner of the screen
- Click the name of the played video
- Observe the progress bar
Expected result
- Progress bar reflects the state of the ongoing played video
Actual result:
- Progress bar is not working
Regression range
- This doesn't look to be a regression, reproducible way back to Fx 87.a01
Other notes
- Not reproducible on Chrome
- Arm configuration is affected as well
Reporter | ||
Updated•3 years ago
|
Has STR: --- → yes
Comment 1•3 years ago
|
||
This is a known issue, we haven't implemented this yet.
Blocks: media-control
Updated•11 months ago
|
Assignee: nobody → nerixdev
Status: NEW → ASSIGNED
Comment 3•11 months ago
|
||
Comment on attachment 9391339 [details]
Bug 1739151 - Guess position state from media elements. r=alwu
Revision D204691 was moved to bug 1887128. Setting attachment 9391339 [details] to obsolete.
Attachment #9391339 -
Attachment is obsolete: true
Updated•4 months ago
|
Updated•4 months ago
|
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
status-firefox133:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
Updated•4 months ago
|
Component: Audio/Video → Audio/Video: Playback
Updated•4 months ago
|
Updated•4 months ago
|
Flags: qe-verify+
Comment 5•3 months ago
•
|
||
I've replicated this issue using Nightly 96.0a1 (2021-11-03) on macOS 13 following the STR from Comment 0.
Verified as fixed in the latest Nightly 134.0a1 (2024-11-03) and Firefox 133.0b3 version on macOS 13 as the issue no longer occurs.
You need to log in
before you can comment on or make changes to this bug.
Description
•