Closed Bug 393221 Opened 18 years ago Closed 15 years ago

XMLHttpRequest call onreadystatechange with "this" set to the wrong object

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: manixrock, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 XMLHttpRequest call onreadystatechange with "this" set to the function instead of the object Reproducible: Always Steps to Reproduce: var req = new XMLHttpRequest; req.open("GET", "http://localhost/doc.txt", false); req.onreadystatechange = function() { document.write("this: "+this); }; req.send(null); Actual Results: this: function () { document.write("this: " + this); } Expected Results: this: [object XMLHttpRequest] in IE and Opera "this" correctly point to the XMLHttpRequest object.
Version: unspecified → 2.0 Branch
Just came across this, looks like it could be another: "synchronous XMLHttpRequest does not fire "readystatechange" event" https://bugzilla.mozilla.org/show_bug.cgi?id=313646
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.