These are chat archives for HackedByChinese/ng-idle

22nd
Jun 2016
Mike Grabski
@HackedByChinese
Jun 22 2016 01:56
@akshitsawhneyseedoc Well, many browsers greatly throttle the execution of scripts running in background tabs, so these inactive tabs don't steal performance from the active tab.
However, ng-idle should do a check once you come back to a tab and do something to see if the time since the last activity exceeds the idle duration and jump right to IdleTimeout event. You would not even see IdleStart or IdleWarnevents, so if you're counting on those to show up, this should help you understand why you aren't seeing them.
Mike Grabski
@HackedByChinese
Jun 22 2016 02:02
Starting with v1.2, windowInterrupt() option was added to allow you to interrupt based on window events. The natural use case is check the idle state when a user brings a window or inactive tab into focus. E.g. windowInterrupt('focus');