W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

[Bug 25969] New: [XHR] Does "process response body" get processed even if the XHR is abort()-ed in readystatechange?

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Jun 2014 04:27:25 +0000
To: public-webapps@w3.org
Message-ID: <bug-25969-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25969

            Bug ID: 25969
           Summary: [XHR] Does "process response body" get processed even
                    if the XHR is abort()-ed in readystatechange?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
          Assignee: annevk@annevk.nl
          Reporter: tyoshino@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

"process response" and "process response body" are separately queued (specified
in fetch.spec.whatwg.org). Even if abort() is called in readystatechange
handler in "process response", it seems we'll run queued task to run "process
response body" and run redundant "Handle errors for response" step and
unexpectedly (I believe) run steps 3 and 4. Don't we want to insert state check
to "process response body" algorithm to skip them, or cancel tasks queued in
the networking task source on termination of fetch?

Or, that "handle the tasks queued" is placed in the step "13. Fetch req ..."
implies that termination of fetch also cancels task handling?

Anyway, it's nice to add some text for clarification.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 4 June 2014 04:27:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC