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
If you open up a page on Safari, and you switch to another app, all network requests and any code running (including setInterval and setTimeout) are paused until you switch back to Safari.
See http://stackoverflow.com/a/4941098/2393627
When you switch back to Safari after some time, the javascript code executes again, including that of RequireJS. RequireJS then checks the time difference of pending network requests and figures out that it's been a long time and times out. The network requests never really had the "time" (in CPU cycles, that is) to be resolved.
RequireJS does not check if the application has been put to sleep and does not offset the time differences accordingly.
The text was updated successfully, but these errors were encountered:
Google chrome also use similar technique. If you switch to other tab, it's seems to halt the loading resources execution. In HTML5, I know there is pageVisibility api to tackle this issue. I'm not sure about iOS safari. Really bug me
If you open up a page on Safari, and you switch to another app, all network requests and any code running (including setInterval and setTimeout) are paused until you switch back to Safari.
See http://stackoverflow.com/a/4941098/2393627
When you switch back to Safari after some time, the javascript code executes again, including that of RequireJS. RequireJS then checks the time difference of pending network requests and figures out that it's been a long time and times out. The network requests never really had the "time" (in CPU cycles, that is) to be resolved.
RequireJS does not check if the application has been put to sleep and does not offset the time differences accordingly.
The text was updated successfully, but these errors were encountered: