W3C home > Mailing lists > Public > public-svg-wg@w3.org > April to June 2008

Progress Event Implementer feedback

From: Andrew Emmons <andrew.emmons@quickoffice.com>
Date: Tue, 3 Jun 2008 12:27:40 -0500
To: W3C SVG Public Working Group <public-svg-wg@w3.org>
Message-ID: <A13D0B44629697468E9C6AE200CFD39A507B81BF61@mailkeeper.mdigitalm.com>
Hello WG,

We've (finally) started implementing Progress Events as defined in the SVGT 1.2 uDOM Appendix. There are a few minor items that we'd like to discuss in an upcoming telcon as implementer feedback:

"The ProgressEvent<http://www.w3.org/Graphics/SVG/Group/repository/spec/mobile/1.2/1.2NG/publish/svgudom.html#events__ProgressEvent> occurs when the user agent makes progress loading a resource (local or external) referenced by an xlink:href attribute."

We would like to discuss the use cases for local resources. It seems to us that it is not worth the implementation burden to support local resources. A use-case I can see is perhaps for base64-encoded local images, where the implementation decodes said images asynchronously. It could also be useful for progressively-rendering UAs.

We would also like to discuss the use cases for progress events on audio and video. For the most part, audio/video files are streamed - even if on a local filesystem the codec does not load the entire media into memory at once. It seems to us that Media Access Events are the proper events to use for audio and video, and as such progress events should not be triggered for these.

We would also like to discuss the bubbling of progress events. As noted at the recent F2F, the WebAPI progress event specification has removed the bubbling  phase for these events. We would like to discuss the merits of bubbling vs not for the SVG progress events.


Andrew Emmons
Engineering Director, SVG Business Unit
Co-Chair, W3C SVG Working Group
Quickoffice, BitFlash Division
Received on Tuesday, 3 June 2008 17:29:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:08 UTC