W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

FW: Question about the ProgressEvent implementation status

From: Vincent Hardy <vhardy@adobe.com>
Date: Thu, 8 Dec 2011 16:49:48 -0800
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <CB063C0E.26321%vhardy@adobe.com>

I sent a question to Anne directly about ProgressEvent and he suggested to send it to a public list. So here is Anne's answers to my questions about the status of ProgressEvent.

Kind regards,

From: Anne van Kesteren <annevk@opera.com<mailto:annevk@opera.com>>
Date: Thu, 8 Dec 2011 09:41:19 -0800
To: "chaals@opera.com<mailto:chaals@opera.com>" <chaals@opera.com<mailto:chaals@opera.com>>, Adobe Systems <vhardy@adobe.com<mailto:vhardy@adobe.com>>
Cc: Ethan Malasky <emalasky@adobe.com<mailto:emalasky@adobe.com>>
Subject: Re: Question about the ProgressEvent implementation status

On Thu, 08 Dec 2011 03:52:15 +0100, Vincent Hardy <vhardy@adobe.com<mailto:vhardy@adobe.com>> wrote:
Since you are the editors of the ProgressEvent spec, I thought you might
be able to help us understand the implementation/adoption status.

I'd prefer if you asked this on a public list next time so everyone can
benefit from the answer.

I believe they are implemented by Webkit/Gecko and soon Opera (12) as far
as XMLHttpRequest is concerned. Not sure about Internet Explorer.

>From what we have gathered, it seems that the spec. is used in SVG Tiny
1.2 (see [1]) which I believe Opera implements (see [2]).

We also see that XHR2 depends on ProgressEvents.

However, it seems the ProgressEvent are not used in the HTML5 spec. for
progress on media element. That may be a basic question, but is that
because of the timing of the specs or is there a technical reasons why
media progress events (see [3]) are not ProgressEvents?

Media ended up wanting to expose a lot of data and it made more sense for
them to expose the data on the elements instead of the event object.

HTML does use them for its application cache feature and that's
implemented by WebKit/Gecko/Opera and the next IE.

Also, back several years ago, there were discussions of having progress
events on all external resources (ala SVG Tiny 1.2). Do you know if
there have been discussions about having that for HTML <img>?

I think we should look at that again once we've more experience with
XMLHttpRequest. That is, I think in the years since that was suggested we
learned it is best to roll these features out in baby steps rather than
wholesale and keep evaluating to see whether it makes sense.

[1] http://www.w3.org/TR/SVGTiny12/svgudom.html#events__ProgressEvent
[2] http://dev.w3.org/SVG/profiles/1.2T/test/SVGT12-ImpReport.html

Anne van Kesteren
Received on Friday, 9 December 2011 00:50:19 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:37 UTC