Firebug 1.4.x breaking AJAX?

10 views
Skip to first unread message

ScottChiefBaker

unread,
Mar 9, 2009, 1:35:37 PM3/9/09
to Firebug
I'm running Firebug 1.4.x with a nightly firefox on Linux. Firebig
seems to break all my ajax requests. Gmail won't load properly, google
maps won't load... I have an intranet with some AJAX on it and it
seems to break that too. Is anyone else having this problem? So far
the only fix I've seen is to suspend firebug and retry the site.

- Scott

Jan Odvarko

unread,
Mar 9, 2009, 4:09:14 PM3/9/09
to Firebug
Which exact version do you use from branch 1.4?

Could it be related to:
http://code.google.com/p/fbug/issues/detail?id=1565
?

Honza

Scott Baker

unread,
Mar 9, 2009, 5:52:03 PM3/9/09
to fir...@googlegroups.com
2009/3/9 Jan Odvarko <odv...@gmail.com>:

>
> Which exact version do you use from branch 1.4?
>
> Could it be related to:
> http://code.google.com/p/fbug/issues/detail?id=1565

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

Jan Odvarko

unread,
Mar 10, 2009, 8:50:33 AM3/10/09
to Firebug
I have a simple XHR test case here:
http://www.janodvarko.cz/firebug/tests/601/Issue601.htm

I see the response within the Net panel and also within the page. Can
you also try it?

If this one doesn't reproduce the bug on your side, could you provide
another simple & focused test that I could use?

Honza

On Mar 9, 10:52 pm, Scott Baker <scott.ba...@gmail.com> wrote:
> 2009/3/9 Jan Odvarko <odva...@gmail.com>:

Thymus

unread,
Mar 10, 2009, 6:46:20 AM3/10/09
to Firebug
I also noticed this issue.

It's like if Firebug would catch the event saying that an ajax request
is done and a response is returned. So, any handler onSuccess,
onFailure etc... won't work.

I use nighly build of Firefox 3.2a1pre and firebug-1.4X.0a12.xpi but I
have the same issue with Firebug 1.3.3 final.

Cheers,

On Mar 9, 10:52 pm, Scott Baker <scott.ba...@gmail.com> wrote:
> 2009/3/9 Jan Odvarko <odva...@gmail.com>:
>
>
>

Thymus

unread,
Mar 10, 2009, 5:37:51 AM3/10/09
to Firebug
I also noticed this issue.
It's like if the onSuccess event or any other event after the end of
an AJAX request was not called due to a trigger catched by Firebug in
place of the JS of the website

I use a nightly build of Firefox 3.2a1pre and firebug-1.4X.0a12.xpi

Cheers,

On Mar 9, 10:52 pm, Scott Baker <scott.ba...@gmail.com> wrote:
> 2009/3/9 Jan Odvarko <odva...@gmail.com>:
>
>
>

Jan Odvarko

unread,
Mar 10, 2009, 12:10:32 PM3/10/09
to Firebug
I believe that this is related to:
http://code.google.com/p/fbug/issues/detail?id=1569

I need a simple test case to fix this.
Honza

Scott Baker

unread,
Mar 10, 2009, 12:55:10 PM3/10/09
to fir...@googlegroups.com
On Tue, Mar 10, 2009 at 9:10 AM, Jan Odvarko <odv...@gmail.com> wrote:
>
> I believe that this is related to:
> http://code.google.com/p/fbug/issues/detail?id=1569
>
> I need a simple test case to fix this.
On Tue, Mar 10, 2009 at 9:10 AM, Jan Odvarko <odv...@gmail.com> wrote:
>
> I believe that this is related to:
> http://code.google.com/p/fbug/issues/detail?id=1569
>
> I need a simple test case to fix this.
> Honza

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

Jan Odvarko

unread,
Mar 10, 2009, 4:31:48 PM3/10/09
to Firebug
There must be a problem with the Firefox nightly build.
I have tested Firebug 1.4 with FF 3.0.7 and it works exactly as
expected - I can see the "STATE_CHANGE!!!!" (4x for every request) in
Firebug's Console panel.

When I am testing with nightly build (I have downloaded from here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/)
It just doesn't work.

Try to disable XHR monitoring in Console (Console panel -> Options ->
ShowXMLHttp requests)
Requests won't be displayed in Console panel, but you can still see it
in Net panel. In this case your code works for me (the line 51 is
executed)

Honza


On Mar 10, 5:55 pm, Scott Baker <scott.ba...@gmail.com> wrote:
> On Tue, Mar 10, 2009 at 9:10 AM, Jan Odvarko <odva...@gmail.com> wrote:
>
> > I believe that this is related to:
> >http://code.google.com/p/fbug/issues/detail?id=1569
>
> > I need a simple test case to fix this.

Scott Baker

unread,
Mar 10, 2009, 8:03:07 PM3/10/09
to fir...@googlegroups.com
On Tue, Mar 10, 2009 at 1:31 PM, Jan Odvarko <odv...@gmail.com> wrote:
>
> There must be a problem with the Firefox nightly build.
> I have tested Firebug 1.4 with FF 3.0.7 and it works exactly as
> expected - I can see the "STATE_CHANGE!!!!" (4x for every request) in
> Firebug's Console panel.
>
> When I am testing with nightly build (I have downloaded from here:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/)
> It just doesn't work.
>
> Try to disable XHR monitoring in Console (Console panel -> Options ->
> ShowXMLHttp requests)
> Requests won't be displayed in Console panel, but you can still see it
> in Net panel. In this case your code works for me (the line 51 is
> executed)

Aha good catch... this will at least let me work around this for a
while. Is this something that should be reported to Mozilla?

Jan Odvarko

unread,
Mar 11, 2009, 7:17:40 AM3/11/09
to Firebug
> Is this something that should be reported to Mozilla?
Yes. If you could report a new bug in bugzilla, attach a test case and
link to this discussion
and cc me (odvarko at gmail dot com) that would be awesome!
Thanks!
Honza

On 11 Bře, 01:03, Scott Baker <scott.ba...@gmail.com> wrote:

ScottChiefBaker

unread,
Mar 11, 2009, 12:19:56 PM3/11/09
to Firebug
I opened a bug for us:

https://bugzilla.mozilla.org/show_bug.cgi?id=482721

You'll have to add your own CC though.

Jan Odvarko

unread,
Mar 11, 2009, 12:23:20 PM3/11/09
to Firebug
OK, I have added myself.
Thanks!

Honza
Reply all
Reply to author
Forward
0 new messages