RESOLVED INVALID 95425
Fire readystatechange event when XHR.send() is called 
https://bugs.webkit.org/show_bug.cgi?id=95425
Summary Fire readystatechange event when XHR.send() is called
Gao Chun
Reported 2012-08-30 00:08:56 PDT
As described in http://www.w3.org/TR/XMLHttpRequest/#the-send-method, if XMLHttpRequest is opened in async mode, readystate event should be fired when send() is called.
Attachments
Patch (11.90 KB, patch)
2012-08-30 00:45 PDT, Gao Chun 		no flags
DetailsFormatted DiffDiff
Patch (13.42 KB, patch)
2012-08-30 06:13 PDT, Gao Chun 		ap: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Gao Chun
Comment 1 2012-08-30 00:45:46 PDT
Created attachment 161413 [details] Patch
Gao Chun
Comment 2 2012-08-30 00:54:16 PDT
The spec said that, if synchronous flag is unset, readystatechange event should be fired after calling XHR.send().
WebKit Review Bot
Comment 3 2012-08-30 05:14:20 PDT
Comment on attachment 161413 [details] Patch Attachment 161413 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13693700 New failing tests: fast/xmlhttprequest/xmlhttprequest-gc.html fast/xmlhttprequest/xmlhttprequest-nonexistent-file.html
Gao Chun
Comment 4 2012-08-30 06:13:48 PDT
Created attachment 161458 [details] Patch
Alexey Proskuryakov
Comment 5 2012-08-30 09:41:22 PDT
Comment on attachment 161458 [details] Patch The latest spec version no longer says that, see <http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#the-send()-method>. When proposing changes like this one, it's necessary to perform detailed analysis. What do other browsers do? If a spec disagrees with browsers, was that a result of deliberation, or just a mistake? As you see, spec drafts change all the time.
Alexey Proskuryakov
Comment 6 2012-08-30 09:42:28 PDT
Marking INVALID as rationale is not correct per latest spec. If you disagree, or if you have additional rationale, please feel free to re-open.
Note You need to log in before you can comment on or make changes to this bug.