W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: 'loadend' event on media elements

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 17 Aug 2009 22:02:02 +0000 (UTC)
To: Jonas Sicking <jonas@sicking.cc>
Cc: Simon Pieters <simonp@opera.com>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0908172201310.6420@hixie.dreamhostps.com>
On Thu, 13 Aug 2009, Jonas Sicking wrote:
> On Thu, Aug 13, 2009 at 7:06 PM, Ian Hickson<ian@hixie.ch> wrote:
> > On Thu, 6 Aug 2009, Simon Pieters wrote:
> >>
> >> The Progress Events spec talks about a 'loadend' event that is to be
> >> fired after load, error or abort. However, HTML5 doesn't say anything
> >> about loadend for <video> and Firefox, Chrome and Safari don't fire
> >> loadend.
> >>
> >> What do we want to do with loadend?
> >
> > On Fri, 7 Aug 2009, Simon Pieters wrote:
> >>
> >> When a media element has <source> children (and no src=''), the load
> >> might never complete, so in that case there would be no loadend event
> >> unless you got an abort or load event. When it has src='', you would
> >> always get a loadend event.
> >
> > What's the difference between 'load' and 'loadend'?
> 
> 'load', 'error', and 'abort' are mutually exclusive. 'loadend' fires
> after any of the three.

Ah, I see. Thanks. Fixed.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 17 August 2009 22:02:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:43 GMT