Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
iauser:iqxanybrowserrecommendations [2021/05/07 11:23] – [IQXanywhere Browser recommendations] Justin Willey | iauser:iqxanybrowserrecommendations [2021/05/07 12:53] (current) – Justin Willey | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== IQXanywhere Browser recommendations ====== | ====== IQXanywhere Browser recommendations ====== | ||
- | IQXanywhere | + | IQXanywhere |
+ | |||
+ | One area which can give difficulty is when the IQXanywhere session is inactive for a period, particularly if it is hidden behind other windows. This is because all browsers try to reduce the resources (memory etc) they consume by deactivating tabs or windows that the believe are not in use. The effect of this is that IQXAnywhere believes that the session has been disconnected. When the browser window is reactivated, | ||
+ | |||
+ | There is currently no way for a connected application or website to indicate to a browser that a connection needs to be maintained, even when the session is inactive. A number of changes have been proposed in the area which IQX will monitor and | ||
While all modern browsers will work the browser that gives IQXanywhere the biggest problems is Chrome. Like the others, Chrome has a built in feature that outs unfocused tabs to sleep - the impact of this being a forced timeout of your session. While IQXanywhere resumes if you have partially completed forms or imputed data this can be lost. Sadly Chrome has permanent no way of mitigating this issue. | While all modern browsers will work the browser that gives IQXanywhere the biggest problems is Chrome. Like the others, Chrome has a built in feature that outs unfocused tabs to sleep - the impact of this being a forced timeout of your session. While IQXanywhere resumes if you have partially completed forms or imputed data this can be lost. Sadly Chrome has permanent no way of mitigating this issue. |