I'm running: firebug-1.4X.0a12.xpi
I look in to that bug. It seems to break ajax requests on all sites.
It's really odd. If I check the "net" tab it shows the request go out,
and get a response. But that response never triggers the browser to
update itself. I don't think http object changes state.
- Scott
I'm at work, so I don't have time to make a SUPER simple test case,
but here's a stripped down version of the ajax search from my site:
http://www.perturb.org/test.php?search=
Go there, and type in "smurf" in the box. Onkeyup for each letter it
should fire an ajax search. You can see firebug SEND the ajax request,
and then receive the response. The code to handle displaying that
response is on line 51 of the ajax.js. You can see the
console.log("STATE CHANGE!!!!") which never fires, and thus the page
never gets updated. It's looks like the xmlhttp.onreadystatechange
event never fires.
I tested ajax calls with jquery and it works fine. It must use some
alternate method for sending queries. I may not check the list until
the end of the day, if you need more info email me directly
(sc...@perturb.org). This bug is a major show stopper, as I can't do
development on some of the sites I need to.
I really don't wanna revert back to FF 3.0. I'll help any way I can Honza.
- Scott
Aha good catch... this will at least let me work around this for a
while. Is this something that should be reported to Mozilla?