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

[progress-events] Update

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 05 Oct 2010 18:22:35 +0200
To: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.vj32fwh364w2qv@anne-van-kesterens-macbook-pro.local>
I offered Charles to take over editing of the Progress Events  
specification and hopefully drive it to completion. Today I wrote a draft  
for ProgressEvent & company inspired by Charles' work:

   http://dev.w3.org/2006/webapi/progress/

I suggest we publish this as a Working Draft.


Relative to the latest Working Draft —  
http://www.w3.org/TR/2008/WD-progress-events-20080521/ — this has been  
changed:

* Allowed the ProgressEvent interface to be used for pretty much anything.  
This helps with HTML5 application caches.
* Defined a restricted subset of it for HTTP requests.
* Made it clear that for cross-origin requests these events present a leak  
of sorts.
* Event types are now suggestions rather than normative. Specifications  
will have to make the final call.
* Added the event type loadend as suggestion; used by XMLHttpRequest.

I still think the interface members have terrible misleading names and  
would happily fix that to make them more similar to the names used for  
<progress> if we can get agreement, but I guess it is too late for that.


Charles' editors draft can be found here:

   http://dev.w3.org/2006/webapi/progress/Progress.html

He made more changes but those have never been picked up by other  
specifications or implementations so I decided to not base it on that.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 5 October 2010 16:23:15 GMT

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