search

tomasbilek / gwteventservice

Automatically exported from code.google.com/p/gwteventservice
Other
0 stars 0 forks source link

Chrome can not finish page loading when the first server call is in Comet-style #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. RemoteEventService#addListener(...) must be the first call of the GWT
application
2. Load the GWT application with Chrome

What is the expected output? What do you see instead?
Chrome can not finish the loading of the page / GWT application.

What version of the product are you using? On what operating system?
GWTEventService 1.0 and GWT 1.5

Please provide any additional information below.
The problem is that Chrome waits till the first server call is finished and
doesn't recognize the server call cycles (re-scheduled server calls). That
issue seems to appear only with the usage of Chrome.

Workaround
Another server call must be finished first.

Solution
The callback method of addListener() must be finshed before the next
scheduled command is started, to increase the compatibility.

Original issue reported on code.google.com by sven.strohschein@googlemail.com on 2 Apr 2009 at 5:23

GoogleCodeExporter commented 8 years ago 
Fixed in trunk. Target version is 1.0.1.

Original comment by sven.strohschein@googlemail.com on 10 Apr 2009 at 7:01

GoogleCodeExporter commented 8 years ago

Original comment by sven.strohschein@googlemail.com on 25 Apr 2009 at 6:23