Prev and Next button appear after revisit the quiz.

Apr 30, 2014

Hi all

I have disabled the Prev and Next button for all the slides.  I have created a custom button to allow reset the quiz. I published the project to both html5 and flash. The flash version works perfectly fine but the issue with HTML5 version is that the "Prev" and the "Next" button would appear after revisiting the quiz (as seen in the picture). They only appear after revisit the quiz.

I am using Storyline Update 1. Is it a bug of this version or I have done something wrong.



47 Replies
Ashley Terwilliger-Pollard

Hi Yang,

I'd also agree that you'd want to update to the newest version update 5 as Jacob mentioned there have been a number of fixes which are detailed here in the release notes.

Also, the previous/next buttons will reappear on a quiz review (using the review button from the results slide) as the user would need  a way to continue navigating throughout the course and Storyline may not know that you set up your own custom buttons. If you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know. We value your feedback.

Ashley Terwilliger-Pollard

Hi Yang,

Are you revisiting the quiz after you've already answered the question? If so, then it sounds like the same behavior as Storyline currently doesn't know that you inserted your own custom buttons but is recognizing that the user needs some way to navigate away from that slide. 

Damon Crumley

I don't understand the reasoning behind forcing the default navigation buttons to appear because "Storyline may not know that you set up your own custom buttons." Then why does the feature to turn off the default navigation exist? Wouldn't any page potentially be without navigation if that's the reasoning you're using?

Damon Crumley

Another person on my team (Dane Boyington) has commented elsewhere on issues we have using custom navigation. It's just very frustrating how much relies on automated features that can't be accessed or replicated through custom navigation. To have the default navigation appear when the developer has expressly disabled that feature could compromise an entire course. The default navigation won't have any custom triggers applied to them that the developer may require. In our work, we use an "IsQuestionActive" variable to determine whether the user has interacted with a quiz in a particular way. We disable default navigation to ensure that this variable has integrity. If Storyline's default navigation can appear in certain situations, then the user could bypass the custom navigation we've setup with its attached triggers. This would make our "IsQuestionActive" untrustworthy, and could cause the user to get trapped on a page (which is ironically the situation you claim this behavior seeks to avoid).

Leslie McKerchie

Hi Damon! I do not see any recent threads by a user with that name, so I was unable to dig a bit deeper into what may be going on with your team, but if you were to disable the Quiz Review, that would eliminate the issue discussed on this thread. You may also want to take a glance at this tutorial and see if states may better fit your needs.

Christie Pollick

Hi, Ayoub -- Sorry for your troubles! As this thread is older and some may no longer be subscribed, if there were any participants you wanted to reach out to directly, you are welcome to use the 'Contact Me' link on their individual profile pages. 

Otherwise, if you'd like us to take a look at your file, you are free to upload here and we'll be glad to run some testing!

Paul Douglas

I've been having this issue for some time (SL7 too like yourself)  and decided to take a brute force approach which seems to be working well so far.

Rather than having to modify the generated HTML output each time (yuck! Who wants to do that?) I add code in the Master slide:

In the Master slide, I add a trigger to Execute Javascript and add the following code:

// since the Quiz in review mode shows the default SL Prev/Next buttons (SL2 Update 7) we force them to hide
var currentStyle = document.getElementsByTagName('style')[0].innerHTML;
//only modify the style tag the FIRST time
if(currentStyle.indexOf("controls") === -1){
document.getElementsByTagName('style')[0].innerHTML = currentStyle + "#controls{ display:none !important;}";

All it does is modify the <style> tag in the HTML5 output, and adds styling for the #controls <div> that houses the pesky Storyline default navigation and sets it to hide. I also add a check to only add this style once rather than potentially many times on a new page visit which could lead to trouble.

Hope it helps.


Paul Douglas

Hi Sudhakar,

I've not been using the built-in navigation buttons at all. They are turned off across the entire course (but annoyingly appear in Review mode anyway - hence my hacky code).

If you're using the built-in navigation for your course, do you even need to hide these buttons in review mode? I thought by default they are still usually needed even in Review mode so the user can navigate forward/backward through the quiz to review each of their answers?

If not, feel free to send me some more details and I'll see if I can assist.


Sudhakar Reddy

Dear Paul,

We are using navigation for entire course except Quiz pool which is having 10 random questions out of 50 with custom submit button. The quiz pool is having question number and it is working properly when we are in review mode. So I decided to add custom next and prev button by using your code. By using your code, question number issue is fixed but bottom navigation button are not appearing after result page. 

Hope this information will help you to understand our concern.

Regards, S

Andrew Helms


No problem at all! Thanks for looking. I'm having trouble seeing the change. In Chrome, everything seems to disappear and not function. If I test in IE, I get everything on screen but the prev next buttons still show up. When I test in our LMS SuccessFactors, I still get the prev/next buttons too. I am at work and am wondering if IT has somehow disabled any javascript from executing. 


Paul Douglas

Hi Andrew,

The hack I described above is designed only to affect the HTML5 output (story_html5.html) as that ALWAYS shows the built-in PREV/NEXT buttons when reviewing a quiz.

I see that even in your flash version (story.html) if I answer the "Pick One" question, get to the Results slide and then return to the "Pick One" the default buttons return. I do not have this issue in any of my courses and I think it's because I don't EVER use ANY of the built-in Storyline controls on ANY slide as they seem to cause more issues than be of any help.

In your course you use the seekbar and as mentioned here:

Ashley Terwilliger says:
Correct - the previous and next buttons are included by default in a quiz review.
If you don't want them to appear at all, you'd need to remove the other player elements such as the volume control and seekbar, as those are in the same line as where the previous/next buttons would appear

In your course "Story View" I selected all slides and ensure all Slide Navigation and Player Features were turned off, republished and the flash version seemed fine. I think then if you add my code in the Top Master Slide it will also prevent the HTML5 only bug where those prev/next buttons would still appear anyway.

So unless you can also remove all built-in nav elements on your course then I'm not sure this situation can be avoided?

Let me know how you go!


Ashley Terwilliger-Pollard

Thanks Paul for including that workaround here - I have noticed that it's only worked for some users - so it's a bit sporadic, but again as we'd expect since the default behavior is to always have the prev/next buttons appear on a revisit to a quiz slide since the user will need a way to submit them. 

Andrew Helms

Yeah, I have to keep that seekbar. That's where I'm running into the issue. I'm confused though. If you don't ever use the default player controls, what's the code for? I thought if you don't use the default controls, then the issue won't affect you? 

Or are you saying the issue does still affect the HTML5 version, even if you don't use the default player controls? 

Also, if you look at Sudhukar's comment on my project above, he says that the code is working for him when he reviews my quiz slides. Very odd. Haha. I'm going to submit another feature request. It seems like this has been requested several times already. I don't know why it's so difficult to turn off a default option that nobody wants.