1225878 - onprogress event not fired correctly

Status: UNCONFIRMED

(Core :: DOM: Events, defect, P5)

Description

[Dima Sokol]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

1. Add listener for media events
var events='abort canplay canplaythrough durationchange emptied ended error loadeddata loadedmetadata loadstart pause play playing progress ratechange seeked seeking stalled suspend timeupdate volumechange waiting';
$('#myAudioTag').on(events, function(e){
  console.log(e.type, e.target.duration, e.target.buffered.length ? e.target.buffered.end(0) : null);
});
2. Start playing audio



Actual results:

emptied NaN null
ratechange NaN null
play NaN null
waiting NaN null
loadstart NaN null
progress NaN null
durationchange 242.80399 35.399199
loadedmetadata 242.80399 35.399199
loadeddata 242.80399 35.399199
canplay 242.80399 35.399199
playing 242.80399 35.399199
canplaythrough 242.80399 35.399199
timeupdate 242.80399 35.399199
progress 242.80399 35.399199
suspend 242.80399 35.399199
timeupdate 242.80399 35.399199
timeupdate 242.80399 242.80399 <------- only here we get all track loaded but no onprogress event is fired for this


Expected results:

onprogress should be fired periodicaly during donwloading of audio track

Comment 1

[Alice0775 White]

Dima Sokol, Could you attach a minimized test case or public url?

Comment 2

[Dima Sokol]

(In reply to Alice0775 White from comment #1)
> Dima Sokol, Could you attach a minimized test case or public url?

Here you go http://jsbin.com/yekopogeto/1/edit?html,js,output
After first song load it will be cached so just change https to http and back to make it load song again.

You'll see that on default browser controls load progress goes to the end but event didn't fired.
Actually it fired couple of times, then stops, and when it must be called again (song played to the end of buffered range or seeked there) it just not fired.

Comment 3

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.