-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to change the timeout duration at runtime? #28
Comments
The plugin would need to be modified to accept 'on the fly' configuration changes. I found some resources here: Perhaps you'd like to modify it? |
I have modified the plugin to accept on the fly idleTimeLimit change. And what is the build precess to create the .min.js file. Do I need to create a manually and push it to the git? |
You can check the code changes here |
Great job on the 'on the fly' fork. I will test it soon. To minify, I typically use http://jscompress.com/ |
I do not have time to work on this code right now. In the future, I hope to make the plugin easier to maintain by separating the iframe functionality into a separate script that could be loaded if needed. Right now, I have too much duplicate code, so makes it more difficult to make improvements to the code package. |
Hi,
I have a use case where a parent domain can have multiple applications and each application can have different timeout. But to have the consistency, the max timeout of the opened application will be used.
The timeout can be stored in local storage and can be shared with all the opened application of that particular parent domain. But how to change the timeout duration at run time without re-instantiating the idleTimeout plugin?
The text was updated successfully, but these errors were encountered: