Michael, Actually, while I was waiting I did a test---I can successfully cancel an upload, but I get no ready state change after I manually abort.
Garret On Nov 10, 8:56 pm, Michael Nordman <[EMAIL PROTECTED]> wrote: > Hi Garret, > The request object transitions to the 'complete' ready state (4) and the > req.status property accessor will throw an exception after the request has > completed due to a network error or an explicit call to abort. > > On Mon, Nov 10, 2008 at 8:45 PM, Garret Wilson <[EMAIL PROTECTED]>wrote: > > > > > Austin, > > > Thanks for the reply, but it was terribly vague. > > > "...thus carries the same fate..."---what fate is that? > > > "...in a particularly direct fashion."---what particular fashion is > > it, then? > > > Perhaps the "fate" isn't "particularly direct", but surely *something* > > happens. I need to know what that "something" is, because it isn't > > documented. > > > * When a network error occurs, what does the readyState change to? > > > * When a network error occurs, is onprogress() called, and with what > > values? > > > * When I cancel an upload, what does the readyState change to? > > > * When I cancel an upload, is onprogress() called, and with what > > values? > > > Regardless of whether XHR is well documented, Gears is a Google > > produce that presumably has some deterministic behavior in the > > presence of errors. Why can't that be documented? > > > Garret
