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 <[email protected]> wrote: > Which version of Firefox 3.5? If you have a 3.5 beta, update to the > release candidate builds first. > jjb > > On Jun 25, 10:49 am, Sebastien <[email protected]> wrote: > > > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
