W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

[ProgressEvents]

From: Erik Dahlström <ed@opera.com>
Date: Sun, 07 Sep 2008 17:47:18 +0200
To: "public-webapps@w3.org" <public-webapps@w3.org>, "Charles McCathieNevile" <chaals@opera.com>
Cc: public-svg-wg@w3.org
Message-ID: <op.ug4bg4p3gqiacl@gnorps.linkoping.osa>

Hello webapps wg,

On behalf of the SVG WG I'd like to propose adding to the ProgressEvents spec[1] an event equivalent to the 'loadend' (previously known as 'SVGPostLoad') event currently defined in SVG Tiny 1.2 [2].

The 'loadend' event is dispatched by completion of a load, no matter if it was successful or not. In terms of the ProgressEvents spec the 'loadend' event would be dispatched following either of 'abort', 'load' or 'error', and there must be exactly one 'loadend' event dispatched. In the Event definitions table it would look like this:

Name: loadend
Description: The operation completed
How often?: once
When?: 	Must be dispatched last

The SVG WG have aligned the other ProgressEvent event names[3], and have made changes to make these events compatible with the ProgressEvents 1.0 spec.

Cheers
/Erik, on behalf of the SVG WG, (ACTION-2159)

[1] http://dev.w3.org/2006/webapi/progress/Progress.html
[2] http://dev.w3.org/SVG/profiles/1.2T/publish/interact.html#EventsPostload
[3] 'SVGPreLoad' -> 'loadstart' and 'SVGProgress' -> 'progress'

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Sunday, 7 September 2008 15:47:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT