[Bug 27033] XHR request termination doesn't terminate queued tasks

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27033

--- Comment #13 from Anne <annevk@annevk.nl> ---
(In reply to Hallvord R. M. Steen from comment #10)
> As far as I can tell, all implementations change to 4 due to abort() and 1
> due to open() (even when open() is called during abort processing). This is
> pretty consistent.

Are you saying that they do not eventually change it to UNSENT in case of
abort() (when open() is not called)? Because I believe that part of the
specification is actually tested.


> * Webkit (as seen in Opera and Chrome, Safari not tested) doesn't fire any
> onabort events at all if you call abort() in the OPENED state. Hence these
> tests aren't really valid in Webkit-based browsers. If we want to require
> these abort events to fire, we can probably just ignore the Webkit family
> for now.

This is OPENED with the send() flag set, correct?


> It may be noteworthy that implementations consistently let open() prevent
> the abort processing's onloadend event from firing. AFAIK the spec is out of
> tune with implementations here.

So if that's the case we'd need to add a new flag "open()/abort() flag" or some
such, that is checked before an event is fired.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 20 October 2014 15:18:10 UTC