Re: [XHR2] final progress events

2011-06-21 Thread Glenn Maynard
On Tue, Jun 21, 2011 at 12:01 PM, Anne van Kesteren wrote: > I think we would also want to dispatch it just before timeout, error, and > abort, no? HTML and the File API would probably also be affected by this > somehow. File API being modeled after XMLHttpRequest, and XMLHttpRequest > after HTML.

Re: [XHR2] final progress events

2011-06-21 Thread Anne van Kesteren
On Thu, 17 Mar 2011 19:40:23 +0100, Glenn Maynard wrote: I suggest requiring that a progress event be fired when loaded == total, regardless of the 50ms interval timer. WebKit appears to already do this in all cases: xhr.onprogress is always sent before readyState is changed to DONE, and xhr.up

Re: [XHR2] final progress events

2011-03-17 Thread Olli Pettay
On 03/17/2011 09:09 PM, Olli Pettay wrote: On 03/17/2011 08:40 PM, Glenn Maynard wrote: From https://bugzilla.mozilla.org/show_bug.cgi?id=637002: If you leave this as invalid, would it at least be possible (or even necessary) to fire the progress event one last time (e.g. right when finished

Re: [XHR2] final progress events

2011-03-17 Thread Olli Pettay
On 03/17/2011 08:40 PM, Glenn Maynard wrote: From https://bugzilla.mozilla.org/show_bug.cgi?id=637002: If you leave this as invalid, would it at least be possible (or even necessary) to fire the progress event one last time (e.g. right when finished sending all bytes without waiting for the se

[XHR2] final progress events

2011-03-17 Thread Glenn Maynard
>From https://bugzilla.mozilla.org/show_bug.cgi?id=637002: >> If you leave this as invalid, would it at least be possible (or even >> necessary) >> to fire the progress event one last time (e.g. right when finished sending >> all >> bytes without waiting for the servers response) and to set evt.