Whenever the Chrome tab showing the Salix App is inactive (because another tab has the focus) the Javascript request seem to 'stop' (or better, buffered). When the tab is made active again all the buffered requests are send.
Best example of this is the Clock App. The clock quickly catches up after an inactive period of the tab.
Maybe switching to websockets (full duplex communication) could solve this issue (see #4 )
Whenever the Chrome tab showing the Salix App is inactive (because another tab has the focus) the Javascript request seem to 'stop' (or better, buffered). When the tab is made active again all the buffered requests are send.
Best example of this is the
Clock App. The clock quickly catches up after an inactive period of the tab.Maybe switching to websockets (full duplex communication) could solve this issue (see #4 )