Forum Discussion
Spam-clicking "Next" will bypass logic intending to prevent further slide progress.
Hi DeveloperIgniti,
Thanks for confirming, and thanks to JudyNollet for pointing out how slide transitions affect when Storyline recognizes the timeline start.
I understand that knowing why this happens doesn't necessarily address the concern. To make sure I capture your feedback accurately, are you requesting an enhancement where the built-in Next button starts in a disabled state by default when a slide loads and is enabled only when appropriate? Or did you have a different solution in mind?
Hi EricSantos​. I think there's a few options...
- After user clicks NEXT, wait for some reasonable time before checking to enable NEXT again - e.g. 3 seconds (I can't imagine many people have page transitions lasting more than 3 seconds).
- Have an internal function that checks if a logic block has been added to disable NEXT when Timeline starts on the next slide, and make that trigger take effect when the page transition starts, not when the Timeline starts.
- Add a global option somewhere to have NEXT always disabled by default until custom logic says otherwise.
Turn off the built-in Next button. Create your own, that appears only after 3 seconds?
Hi DeveloperIgniti,
Thanks for taking the time to share those additional suggestions, and thanks as well to everyone who chimed in with explanations and workarounds.
I appreciate you taking the time to share several possible approaches. It's helpful to understand that the goal is to close that timing gap so the intended navigation restrictions are enforced consistently.
I've shared your feedback with our product team, including the examples you provided of possible approaches to address this behavior. We'll let you know if we have any updates to share in the future.
