Forum Discussion
Prev and Next button appear after revisit the quiz.
Sudhakar,
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.
-Andrew
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:
https://community.articulate.com/discussions/articulate-storyline/do-not-want-default-navigation-button-when-revisiting
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!
- AndrewHelms-f1f9 years agoCommunity Member
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.