Firebug 1.4-1.5, FF3.5, Comet and JSON

21 views
Skip to first unread message

Sebastien

unread,
Jun 25, 2009, 1:49:33 PM6/25/09
to Firebug
Hi all,

We have an AJAX application that uses the Comet technology and JSON.
So we have a channel hanging until the backend returns a message.

Everything was well in all browsers, including FF3.0.11 and Firebug
1.3.

But recently I upgraded to FF3.5 and Firebug 1.4 and then 1.5, but we
have serious issues, and I'm not sure what's the reason. It may have
to do with the new inbuilt JSON parser for Firefox.

So when Firebug is running, after 2 or 3 Comet calls, the JSON string
does not seem to get parsed anymore, and therefore it's not treated.
It seems to be random, and when firebug is off, it seems to work
(almost) reliably.


Any ideas?

Seb

johnjbarton

unread,
Jun 25, 2009, 2:00:45 PM6/25/09
to Firebug
Which version of Firefox 3.5? If you have a 3.5 beta, update to the
release candidate builds first.
jjb

Sebastien

unread,
Jun 25, 2009, 2:09:47 PM6/25/09
to Firebug
I have RC3

Sebastien

unread,
Jun 25, 2009, 2:14:10 PM6/25/09
to Firebug
Actually, I don't think it's the JSON parser which is the problem...
the string is returned, firebug catched it and displays it, but the
code never makes it inside my:
onSuccess:function(response){
...
}

On Jun 25, 7:00 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:

johnjbarton

unread,
Jun 25, 2009, 4:07:12 PM6/25/09
to Firebug
I suggest you try Firebug 1.4 on Firefox 3.0 to divide the problem
between Firebug and Firefox.

If it is Firebug, try the tracing version 1.4X: see
http://groups.google.com/group/firebug/web/faq-about-firebug
Trace ERRORS NET and WINDOW

jjb

Sebastien

unread,
Jun 26, 2009, 6:07:10 AM6/26/09
to Firebug
Ok, so now I'm running FF3.0.11 with Firebug 1.5 and it works fine.
So it seems to be firefox related....

Thanks for help.

Seb

On Jun 25, 9:07 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> I suggest you try Firebug 1.4 on Firefox 3.0 to divide the problem
> between Firebug and Firefox.
>
> If it is Firebug, try the tracing version 1.4X: seehttp://groups.google.com/group/firebug/web/faq-about-firebug

johnjbarton

unread,
Jun 26, 2009, 10:46:28 AM6/26/09
to Firebug
Thanks, then we need a test case or public URL that shows the problem.
We can help sort out why Firebug is involved but its likely we will
need help from Firefox team.
jjb

Sebastien

unread,
Jul 4, 2009, 12:05:10 PM7/4/09
to Firebug
Couldn't get around to create a test case since I thought it had
somehow to do with my code.
However, just found the following: https://bugzilla.mozilla.org/show_bug.cgi?id=501962

This is the exact problem I have, and like the author, it randomly
stops working.

Regards,
Seb

johnjbarton

unread,
Jul 4, 2009, 12:49:58 PM7/4/09
to Firebug
1.5a8 has one more fix related to ajax code.

jjb

Sebastien

unread,
Jul 4, 2009, 1:05:01 PM7/4/09
to Firebug
I have 1.5a8 and FF3.5 but the problem remains.

Regards,

Seb

johnjbarton

unread,
Jul 5, 2009, 11:39:02 AM7/5/09
to Firebug
Then we need a test case posted to our issues list,
http://code.google.com/p/fbug/issues/list

jjb

Sebastien

unread,
Jul 5, 2009, 11:48:20 AM7/5/09
to Firebug
Done.
This case is particular relevant in my case: http://sendsome.org/kunden/XNG/test.html
Most of the time, results don't all come.

Regards,

Seb

On Jul 5, 4:39 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> Then we need a test case posted to our issues list,http://code.google.com/p/fbug/issues/list
Reply all
Reply to author
Forward
0 new messages