Open Bug 1506617 Opened 7 years ago Updated 3 years ago

When an audio file is being streamed using html5, clicking on a download link to another file causes the stream to be aborted

Categories

(Core :: Audio/Video: Playback, defect, P5)

defect

Tracking

()

People

(Reporter: singh.karanvir21, Unassigned)

Details

(Keywords: parity-chrome, parity-edge)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce: Go to the website: https://gurmatsangeetcollection.org Play any track on the site and then click the download button on another track. After a few seconds (depending on how much of the stream is already downloaded into memory), the currently playing track will stop playing. Actual results: The originally streaming audio stops streaming. Expected results: It should continue streaming.
Summary: When an audio file is being streamed using html5, clicking on a download link to another file causes the stream to be aborted. This does not happen on Microsoft Edge. → When an audio file is being streamed using html5, clicking on a download link to another file causes the stream to be aborted
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 63 Branch → Trunk
I had difficulty reproducing this. I did reproduce twice with 62.0.3 on https://www.gurmatsangeetcollection.org/collection/SWkG4WGgi6L2hfDdY playing track 1 and downloading track 3. When playback stopped, the site reported an error and the Web Console had a single message: TypeError:e._sounds[0] is undefined I didn't reproduce with 63, but one download stalled.
Component: Audio/Video → Audio/Video: Playback
Priority: -- → P5
(In reply to Karl Tomlinson (:karlt) from comment #1) > I had difficulty reproducing this. > I did reproduce twice with 62.0.3 on > https://www.gurmatsangeetcollection.org/collection/SWkG4WGgi6L2hfDdY playing > track 1 and downloading track 3. > > When playback stopped, the site reported an error and the Web Console had a > single message: TypeError:e._sounds[0] is undefined > > I didn't reproduce with 63, but one download stalled. You're right, I somehow missed that message in the console. I do get the message in 63.0.1 as well. However, both Chrome and Edge had no error messages or stalls when downloading. I will investigate further on my end to see if there's a bug somewhere.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.