Some users report that after answering a question, returning to the answered question using the previous button shows the question with the SUBMIT and not the NEXT/PREV buttons. Learners get stuck in this context. SUBMIT does nothing.
Has anyone seen this and is there a fix/workaround? I can't reproduce the issue.
Hey Sam - Certainly hard to assist when you are unable to reproduce the issue. Do you know if this is in a particular environment/browser that they learners are viewing in?
Sam - it was ringing a vague bell for me as well and I was able to find some information this morning.
It is an issue that has been filed with our QA Team. I do not have an update at this time and we do not have a workaround listed. I do see, however, where a user here mentioned working with support and getting around her issue a bit. Not sure if this will assist you as well.
It does still exist within Storyline 360 - and has been reported to our team as such, but as you've seen the reproducibility of it has been inconsistent for our team as well, so that always makes it a bit trickier to figure them out but it's something we continue to keep an eye on in terms of impact.
5 Replies
Hey Sam - Certainly hard to assist when you are unable to reproduce the issue. Do you know if this is in a particular environment/browser that they learners are viewing in?
I've seen this bug before. I don't know what causes it. I was hoping others had seen this issue and would chime in with more info.
Sam - it was ringing a vague bell for me as well and I was able to find some information this morning.
It is an issue that has been filed with our QA Team. I do not have an update at this time and we do not have a workaround listed. I do see, however, where a user here mentioned working with support and getting around her issue a bit. Not sure if this will assist you as well.
Sounds like a bad problem if it has been around for a year and not yet fixed.
Is there any evidence that SL 360 has fixed this issue?
Hi Sam,
It does still exist within Storyline 360 - and has been reported to our team as such, but as you've seen the reproducibility of it has been inconsistent for our team as well, so that always makes it a bit trickier to figure them out but it's something we continue to keep an eye on in terms of impact.
This discussion is closed. You can start a new discussion or contact Articulate Support.