- From: Maciej Stachowiak <mjs@apple.com>
- Date: Tue, 6 Mar 2007 13:37:15 -0800
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: public-webapi@w3.org
Hi Boris, On Mar 6, 2007, at 1:21 PM, Boris Zbarsky wrote: > > > In brief, the idea is to use the same set of events > > for upload and download, but to provide a separate EventTarget > > attached to the XMLHttpRequest object, which is the target all the > > upload-related events; XHR itself only dispatches the download > events. > > Out of curiousity, is that last a hard requirement? I'm glad you chimed in, since I remember you mentioning Mozilla's plans for progress events. > That is would an implementation which dispatches the upload events > both as "progress" events on xhr.upload and "uploadprogress" events > on xhr be conformant to the specification. If so, that would allow > existing code to continue working while allowing spec-compliant > code to also work. > > I realize that there is an issue with providing non-standard ways > to do what the standard allows in that authors might use code that > works in one UA but not others. So I'm not even sure doing the > above would be a good idea. But would it be allowed per the standard? I don't think any standard forbids dispatching additional events, though you are correct that doing so creates interoperability risks. Out of curiosity, has Mozilla already shipped a product that has the "uploadprogress" event? Is it used by web content, or just by chrome/ extensions? How widespread is the use? Regards, Maciej
Received on Tuesday, 6 March 2007 21:37:30 UTC