You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the user clicks a link in Chrome, the browser cancels all outstanding requests. This causes problems if the link does not cause the page to be unloaded, e.g. if the link goes to a mailto url or something that starts a download instead of loading a new page. Just reopening the streaming/long-polling XHR will not work because Chrome silently ignores any XHRs opened until it realizes that the page will indeed not get unloaded.
I have investigated this situation in a different context. The only reliable way that I then found for handling this is to keep doing send() on the same XHR object until you get an exception saying that the XHR has already been opened or until you observe that the readystate is no longer 1. See http://dev.vaadin.com/ticket/8891#comment:9 for details.
Tested using the chat sample from the head of the atmosphere-1.0.x branch by adding a mailto-link to the page.
The text was updated successfully, but these errors were encountered:
The situation is however slightly different there as there is typically not any connection that should be kept open all the time but instead just avoiding issues if a request is pending while the user does something.
When the user clicks a link in Chrome, the browser cancels all outstanding requests. This causes problems if the link does not cause the page to be unloaded, e.g. if the link goes to a mailto url or something that starts a download instead of loading a new page. Just reopening the streaming/long-polling XHR will not work because Chrome silently ignores any XHRs opened until it realizes that the page will indeed not get unloaded.
I have investigated this situation in a different context. The only reliable way that I then found for handling this is to keep doing send() on the same XHR object until you get an exception saying that the XHR has already been opened or until you observe that the readystate is no longer 1. See http://dev.vaadin.com/ticket/8891#comment:9 for details.
Tested using the chat sample from the head of the atmosphere-1.0.x branch by adding a mailto-link to the page.
The text was updated successfully, but these errors were encountered: