Feature request: delay option
See original GitHub issueIt would be nice to have a delay option, which will only show the progress bar if .done
was not already called within the delay time:
NProgress.configure({delay: 80}) // Only show if not done within 80ms
Issue Analytics
- State:
- Created 7 years ago
- Reactions:14
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Feature request response email templates - LiveAgent
Answer feature request emails professionally and kindly regardless of the (good or bad) news you're delivering to your customers.
Read more >179 delay option for multiline commands - YAT
#179 delay option for multiline commands ... This feature request already implemented by keyword \!(Delay), therefore setting this feature ...
Read more >[feature request] Delay Javascript - WordPress.org
Dear Developer, Giving users the ability to delay the JavaScript of the Instagram plugin until the main page has loaded will significantly improve...
Read more >10 Tips for Responding Graciously to Customer Feature ...
10 Tips for Responding Graciously to Customer Feature Requests · 1. Be open and honest · 2. Be grateful for their effort ·...
Read more >Feature Request: Notification Escalation / Delay ... - GitHub
Related to this, I think we need an option to delay notifications in general. What if you want the service marked as down...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@msurdi I believe you could simplify that to:
To quote https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/clearTimeout:
And https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout says:
So it’s fine to run
clearTimeout
without checking first – it won’t explode on null or old values, and values won’t be reused.I’ve extended @fracz idea to avoid patching the library, in case anyone else finds it useful:
just use
startProgressBar
andstopProgressBar
instead ofnprogress.start/done