On 23/07/2010 8:57 p.m., Philip Jägenstedt wrote:
On Fri, 23 Jul 2010 05:25:37 +0200, Chris Pearce <ch...@pearce.org.nz>
wrote:
Should we be periodically firing a "stalled" event at the media
element while we've suspended download of a preload:none or
preload:metadata media?
[...]
I think this is a spec bug. When a UA decides to not download more
data it should fire the suspend event. It doesn't make any sense to
also fire the stalled event, in my opinion, but the spec isn't clear
about this.
I agree. We should make the spec clearer here.
Also, I don't understand why the stalled event would be fired
periodically in any case, why would that be so?
Agreed, it doesn't make sense to fire multiple stalled events; you can
detect when the download resumes by listening for subsequent progress
events.
On 23/07/2010 5:11 p.m., Silvia Pfeiffer wrote:
To me, stalled implies that the UA is trying to receive stuff, but is
being stalled. So, my understanding is that the resource fetch
algorithm in [1] should include the word "unexpectedly" - that would
fix it.
I think this suggested wording change would be a good one.
Regards,
Chris Pearce.
