W3C home > Mailing lists > Public > public-webapi@w3.org > January 2007

Re: Progress event spec

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 30 Jan 2007 21:11:57 +0100
To: jean-claude.dufourd@streamezzo.com
Cc: Web API public <public-webapi@w3.org>
Message-ID: <3r8vr25orcgd6q1evpcjip8vn6fn72d8n6@hive.bjoern.hoehrmann.de>

* Jean-Claude Dufourd wrote:
>JCD: take a scene with a media element with an empty xlink:href. The 
>load event on the media element arrives at the end of the parsing of the 
>element, because of the empty (or absent) xlink:href.

When the load event occurs in this case is subject to the specification
of this media element. If this media element has embedding semantics, an
empty xlink:href attribute would result in infinite recursion; generally
such a media element cannot load successfully and I would consequently
not expect the load event to occur but the error event to occur instead.

>I suppose that the recording is stopped by a mean resident on the camera 
>(button). From the point of view of the media element, there is no way 
>of  knowing about the end of the media.
>I would like to have:
>- an event at the beginning of the recording, to start a "recording" 
>animation
>- I do not care about events during the recording, because the duration 
>is unknown, so I have no way of slaving my animation to any "progress" 
>indication representing completeness
>- I want an event at the end of the recording, in order to terminate the 
>"recording" animation.

It seems that if the implementation knows about the end of the recording
it also knows about the end of the media, so I am not really sure what
you are trying to say.

>> I also don't want to encourage authors to rely on this event, since doing so 
>> breaks backward compatibility for no good reason that I can understand.
>>   
>JCD: I do not get the "breaking backward compatibility". Would you 
>please clarify ?

He means compatibility with downlevel clients that do not support the
new event. Obviously, if content relies on something that a client
does not support, the content does not work correctly in that client.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 30 January 2007 20:11:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT