Does ng-idle activation module specific?

[gitfortee]

I opened few browser tabs (in the same window) each from two different modules but I observe the tabs that belong to the same module show the idle warning and when i do some activity in only one of those tabs, the idleness is reset on all other tabs that pertain to the same module as the tab in which the idle is interrupted.

Similarly, when i kept the tabs that belong to module1 idle and do some interruptions in the tabs that belong to module2, I see the idleness in the tabs pertaining to module1 is not interrupted.

This makes me to think that ng-idle is module specific.

by the way, my application has different websites. and each website is designated as different module which all share a common/app module where i wrote my ng-idle logic.

I depend on the answer to understand how ng-idle will work/behave if i open my screens in different tabs.

[gitfortee]

@HackedByChinese kindly have a look and provide some pointers please.

thanks.

[moribvndvs]

ng-idle coordinates idle state by storing the last activity timestamp in sessionStorage. Therefore, all tabs/windows to the same domain (even if different pages or ng applications) will use the same expiration. A request was put in to allow devs to key each application so they have different timeouts. I can look into that further.

[gitfortee]

thank you for the response. i will keep a watch. thanks.