Open GoogleCodeExporter opened 9 years ago
The messages are received when a new tab is opened. But then (is seems a retry)
the same message is resend twice after after you click ok on a message-window.
So the number of message is exploding.
Original comment by rvan...@casema.nl
on 11 Feb 2011 at 10:40
I have also seen this behavior on IE8 in development - works fine on chrome 9.x
and 10.x. I have not tested after deployment using IE8.
Original comment by Qagw...@gmail.com
on 1 Mar 2011 at 4:11
In IE8 production mode it is working fine.
I think this is not an issue of this wrapper but it is an issue of the dev mode
javascript code.
Original comment by buchholz...@googlemail.com
on 4 Mar 2011 at 4:42
Does this work in IE7 when the app is deployed in production?
Original comment by jasonhall@google.com
on 4 Mar 2011 at 4:46
Yeah just tested my app in IE7 after deployment and works fine.
Took some time to find a windows version where IE7 is installed or could be
installed...
Finally found an old Vista CD!
Original comment by buchholz...@googlemail.com
on 5 Mar 2011 at 5:46
Yes. I have seen same issues on IE8. could not receive Channel messages even
though socket is opened.
Original comment by email2a...@webappservice.net
on 18 Jun 2011 at 8:02
I have the same problem with IE7.
Messages are not received by IE7, but it's working in firefox 5.
When testing in local, messages are received when opening a new tab in IE7
(messages are send many time), but it doesn't do the trick when the app is on
app engine.
Have to go back to polling I think, the app must work with IE7 :(
Original comment by math.cla...@gmail.com
on 21 Jul 2011 at 7:51
Not working on IE8. Connects successfully with channel, however no message is
received.
Same application is working fine with Chrome and Firefox. Even works fine with
deprecated IE6.
gwt-gae-channel: 0.4 alpha
OS: Windows 7
Original comment by alokkush...@gmail.com
on 2 Aug 2011 at 2:37
Works fine in production mode in IE8
Original comment by alokkush...@gmail.com
on 2 Aug 2011 at 3:11
Original issue reported on code.google.com by
rvan...@casema.nl
on 11 Feb 2011 at 9:41