Closed
Bug 1269078
Opened 10 years ago
Closed 9 years ago
Video playback does not stop, even after closing the tab or loading a new page
Categories
(Firefox for Android Graveyard :: Audio/Video, defect)
Tracking
(firefox49 verified)
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | verified |
People
(Reporter: jan.manthay, Unassigned)
References
()
Details
When loading and playing a video (like http://www.tagesschau.de/wirtschaft/oeffentlicher-dienst-tarifabschluss-101.html), Firefox does not stop the playback even after the tab is closed, or a new page is loaded within this tab. You can still hear the sound.
Firfox has to be forced closed for the replay to stop.
All my devices are affected, Moto G, Asus Memopad HD7, Kindle Fire 5th.
Comment 1•10 years ago
|
||
I cannot see this problem on my HTC M9+.
Jan,
Could you provide your version of Firefox? You can find it by typing "about:" in url field and entering it.
It may be very helpful if you can make a record video to show us how you repro this problem and attach to this bug.
Thanks!
Flags: needinfo?(jan.manthay)
| Reporter | ||
Comment 2•10 years ago
|
||
Version is the latest Nightly 49, from April 30.
Link to a video:
https://www.youtube.com/watch?v=B_0dX6oRtN4
Flags: needinfo?(jan.manthay)
Comment 3•9 years ago
|
||
(In reply to Jan Manthay from comment #2)
> Version is the latest Nightly 49, from April 30.
>
> Link to a video:
> https://www.youtube.com/watch?v=B_0dX6oRtN4
Thanks for this info!
| Reporter | ||
Comment 5•9 years ago
|
||
Looks like this is fixed, can’t reproduce it on Nightly from May 2.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 7•9 years ago
|
||
Verified using:
Device:Galaxy Tab 2
Firefox for Android Aurora - 49.0a2 and Nightly- 50.0a1(2016-05-17)
Updated•9 years ago
|
Comment 8•9 years ago
|
||
I'm changing the status to verified fixed considering that the bug is verified.
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•