tuenti / activity-detector Goto Github PK

activity-detector is only meaningful when running code in a browser, so for a project that uses Universal Rendering (Server Side Rendering) it should not be part of the server side code path.

The problem is that activity-detector tries to unsafely access the document object already during import, which breaks the app before any conditional code paths can be selected. And it is currently not possible to conditionally import modules.

mousemove shouldn't change the state to active if the window is not focused. Or, at least, this feature should be optional.

If we have the same app in 2 tabs it will not reset the timer if I'm using it in only one tab.
We should probably keep the timer in local storage or...

Is there an upper limit of some kind to timetoIdle? I'm using this to implement an auto logout. In tests at one minute or less, it works great. But when I set timeToIdle to 1800000, it fires the idle callback after about 10 seconds.

@atabel, It would be great if you can add support for type definitions.

Hi,

We're having some problems on iOS. The main problem is that activity-detector is not detecting than a user is navigating when VoiceOver is enabled.
Someone has experimented the same issue?

Cheers!

As much as I dislike doing that, I need to use your lib (thanks for the work) with IE8.
There's not much required to make it happen, only issue is lack of addEventListener.
I am inclined to PR a fix.

In the file webpack.config.js, the output.library value should be ActivityDetector, not activityDetector.

What's the best way to remove 'blur' from the inactivityEvents array?

Would you be willing to accept a PR that adds this feature? Maybe via inactivityEvents: undefined?

I'd prefer to not "short-circuit" the timeToIdle timeout.