RESOLVED INVALID 20179
XMLHttpRequest.abort() problem
https://bugs.webkit.org/show_bug.cgi?id=20179
Summary XMLHttpRequest.abort() problem
bugzilla33
Reported 2008-07-26 03:39:16 PDT
1. http://www.w3.org/TR/XMLHttpRequest/#abort 2. browser doesn't switch the state to DONE (4) and doesn't dispatch a readystatechange on XMLHttpRequest.abort() when: a) state is OPENED (1) and send() flag is "true"; b) state is HEADERS_RECEIVED (2); c) state is LOADING (3).
Attachments
Julien Chaffraix
Comment 1 2008-08-02 15:30:30 PDT
(In reply to comment #0) > 1. http://www.w3.org/TR/XMLHttpRequest/#abort I have read again the specification and the code. I did see a small mismatch: we check for state <= OPENED and the send flag is false instead of state == UNSENT or state == OPENED and the send flag is false. However the send() flag is false for the UNSENT state so it should be harmless. > 2. browser doesn't switch the state to DONE (4) and doesn't dispatch a > readystatechange on XMLHttpRequest.abort() when: > a) state is OPENED (1) and send() flag is "true"; > b) state is HEADERS_RECEIVED (2); > c) state is LOADING (3). The 3 last points are covered by a regression test (http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/xmlhttprequest/xmlhttprequest-abort-readyState-shouldDispatchEvent.html). Could you provide us a test case or a real page that shows the bug you are mentioning? And give us all the details about your platform (WebKit revision, OS...)? Thanks!
Alexey Proskuryakov
Comment 2 2009-07-29 17:11:43 PDT
Resolving as INVALID, as there was no response to the above comment, and it's not clear if there is a bug to investigate here.
Note You need to log in before you can comment on or make changes to this bug.