I'm hoping someone can help with this mystery. I've published a course as HTML5/Flash fallback, with menu set to "free" (no restrictions), TinCanAPI, uploaded into an LMS. During QC, we noticed that if the learner navigates linearly, just using PREV and NEXT buttons, no problem with slide chronology. Once they jump around using the menu, and then immediately click PREV or NEXT, it's inconsistent. It jumps anywhere, illogically (forward using PREV occasionally, and backward using NEXT). Only on the first try after jumping to a slide using menu. I can't find other discussions about this specific problem. Does anyone have any suggestions? Thanks so much in advance.
I should also note that this issue is also present when the publish is NOT uploaded into an LMS. It's present even when it's simply hosted by itself on a web server. It doesn't seem related to the LMS.
I sorted out the reason this is happening. It's in the back end programming of the NEXT and PREV buttons. What happens is, when you're navigating through linearly using next, next, next, then you click on the menu and choose another slide, then from whichever slide you're now on, when you hit NEXT or PREV, it is programmed to bring you back to the slide you were on before you used the menu. It's part of the programming. There's a logic to it, but it's definitely jarring to an end user. It's not ideal at all, but apparently it's not a bug. It's been programmed to do that.
4 Replies
I should also note that this issue is also present when the publish is NOT uploaded into an LMS. It's present even when it's simply hosted by itself on a web server. It doesn't seem related to the LMS.
I sorted out the reason this is happening. It's in the back end programming of the NEXT and PREV buttons. What happens is, when you're navigating through linearly using next, next, next, then you click on the menu and choose another slide, then from whichever slide you're now on, when you hit NEXT or PREV, it is programmed to bring you back to the slide you were on before you used the menu. It's part of the programming. There's a logic to it, but it's definitely jarring to an end user. It's not ideal at all, but apparently it's not a bug. It's been programmed to do that.
Hi Melissa,
Thanks for popping back in with an update and for sharing your findings.
You are correct, the Prev button works more like a browser back button and not chronologically.
We've seen requests where users would like to specify this behavior for their courses, so I've added this conversation to this request as well.
I wanted to share some information about how we manage these feature requests as that may be helpful.
Thanks so much, Leslie! I appreciate the reply.
This discussion is closed. You can start a new discussion or contact Articulate Support.