W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2017

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Mar 2017 13:26:43 +0000
To: public-webapps@w3.org
Message-ID: <bug-27033-2927-G9fMkWN5lb@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27033

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #20 from Anne <annevk@annevk.nl> ---
Based on https://github.com/w3c/web-platform-tests/pull/1294 it seems that
Chrome almost never evaluates state after going down the "request error steps"
path and Firefox only after the readystatechange event. I think the simplest is
to keep the standard as-is and just emit some extra events in this rather
contrived scenarios.

I'll file bugs against Firefox and Safari once those tests land.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 8 March 2017 13:26:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:15:04 UTC