Closed
Bug 412112
Opened 17 years ago
Closed 15 years ago
XMLHttpRequest problem with syncronous mode (works with firebug)
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: alberto, Unassigned)
Details
Attachments
(1 file)
|
1.32 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.8.1) Gecko/20061010 Firefox/2.0
If I call the Open method with a XMLHttpRequest object in syncronous mode, it doesn't run the funcion onreadystatechange() (I can't detect if it is in state 1, 2,3 or 4)
Reproducible: Always
Steps to Reproduce:
1.Declare a XMLHttpRequest object
2.Put an alert in the onreadystatechange function
3.make a syncronous call
Actual Results:
Nothing happens.
Expected Results:
it is supposed to display an alert when the object changes its state.
I found in this web more information about this problem (for example, it works if you have firebug installed!):
http://lukav.com/wordpress/2007/04/12/firefox-firebug-and-synchronos-calls-problem/
Comment 1•17 years ago
|
||
You're testing with Firefox 2.0? What about with 2.0.0.11 or 3.0b2?
| Reporter | ||
Comment 2•17 years ago
|
||
The error is fixed in 3.0b2 but not in 2.0.0.11
Comment 3•17 years ago
|
||
Do you know if this is a regression from Firefox 1.5? If it is not, then the bug probably won't get fixed on the 2.0 branch.
Version: unspecified → 2.0 Branch
Comment 4•15 years ago
|
||
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
Comment 5•15 years ago
|
||
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
This seems a duplicate of Bug 313646, which is marked as fixed. Perhaps that bug should be re-opened if the issues still persist, which they seem to based on comment 6 and comment 7.
If you browse in FF 3.6.13 (latest release) to about:buildconfig
you'll see that it was built from http://hg.mozilla.org/releases/mozilla-1.9.2/rev/0c159bd1d600
Looking here: http://hg.mozilla.org/releases/mozilla-1.9.2/log/0c159bd1d600/content/base/src/nsXMLHttpRequest.cpp
you'll see that the fix wasn't backported from trunk.
It also isn't there for upcomming FF 3.6.14 ...
Comment 10•13 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•