The way we tackled this bug in the company I work in was by attaching request IDs to each XHR and when the XHRs returned verifying the ID was the same if it wasn't we fired the request again. Now we may have misdiagnosed the issue as we couldn't find anyone else complaining about this bug when it came to upgrade their web apps to support FF3 but I had presumed that it was down to the fact that our app is considerably more complex then most out there. The possibility that it was Firebug's fault and not FF3 does seem likely to me. If I have time during the week I will test our app without the bug fix to see if I can provide some more feedback.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
