On 18 mai, 14:16, Rasha <[email protected]> wrote:
> I alos found thishttps://bugzilla.mozilla.org/show_bug.cgi?id=407754
Which describes the opposite behavior, i.e. Firefox *waiting* for the
request instead of aborting it.
> so it is a bug in firefox!
I nevertheless do think it is, yes, a bug in Firefox.
BTW, Firefox 2 is discontinued, so you shouldn't base your code on it
(except if you're running your app in an intranet where they haven't
migrated to Firefox 3 and do not intend to do so any time soon...)
Detecting the statusCore == 0 in your onResponseReceived, on the other
hand, is straightforward.
> As I said the only hope is to detect this inside the callback
>
> any idea?
We chose to just ignore the issue (it'll show a "communication error
(status: 0)" in our app, but most if not all our users use IE6, as
it's the company's standard browser)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
