Double-clicking "Next" button allows learner to skip multiple slides

My case is not resolved but I have found the following conditions frequently produce the result:  Restricted navigation with Prev/Next enabled on modern player (HTML5 output obviously) in a course with content that was imported from PowerPoint.  I was NOT successful when trying to reproduce this error with a plain vanilla powerpoint sample, but my guess is that it may be related to the time it takes to make a transition or execute an action or trigger - it only happens if the double click is quite rapid, before the NEXT button becomes disabled.

Thanks for the info, Paul. We definitely have some similarities in our course set-ups. We use:

Restricted navigation
Restricted PREV/NEXT
Modern Player
We never import from PowerPoint. We also incorporate slides that have a variable preventing the user from progressing to the next slide until a certain action flips the variable. When I try double-clicking and the next slide is constrained by a variable, I see the next (correct) slide load, but with our warning message displayed, which tells the user they must complete an action. That message displays when the user tried to click next, which of course they should not even be able to do with restricted navigation, as the slide has not completed (and therefore the next button should not be active).

I'm not sure if any of that info will help you, but thought I'd put it out there. Back before restricted navigation was introduced to Storyline, we used to restrict the next button with a variable on every slide. This could probably still be used as a work-around to this problem, but what a pain!

Thanks for the info Rena, We have VO on every screen and use the feature which prevents the user from dragging the seekbar before the timeline is complete.  It seems to me that there is some action or script activity or transition that occurs on screen load before the next button is disabled, which allows the second click if it is done quickly enough, to work.  I have not seen it happen with content that is not originally imported from powerpoint.

Interesting. We don't use the seekbar, and we don't import from PowerPoint. I think your assessment of what's happening on the back-end is correct; it certainly tallies with what I see on our courses.

We're experiencing the same problem. Did anyone ever find a resolution?

You can use a true/false variable that flips to true once the timeline completes. Then add a condition to the "Next" trigger that the variable must be true. However, this is a huge pain to have to do on each slide. I wish Articulate would just fix the problem.

Same problem.  Does anyone have solution?

Hi Prathmesh and welcome to E-Learning Heroes 😊

Thanks for reaching out and sharing that you're runninginto a similar issue.

I took a look a the support cases that we worked on with some of the above users and it looks like the issue was file specific in each scenario (due to: importing from PowerPoint, corrupt Player) and our team was unable to replicate the behavior in a new file.

I don't have a solution to share with you at this time, but we'd be happy to investigate with you.

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.

I am running into a very similar issue. I have voiceover and media on almost every slide of my course, and when taking the course on an iPad (Chrome or Safari), if I time the clicks just right, I can jump ahead several slides at a time. The navigation in the course (Next/Previous) is restricted in the menu.

It seems like if the next slide hasn't loaded all the way, and there's just a little delay from when the Next button becomes active on the current slide to when the next slide loads and locks the Next button, I can get in there and keep jumping forward.

I'm running v3.46.23620.0. This is also happening on the desktop, though it's slightly harder to replicate, but most of our students are using iPads.