Demonstrable differences between running in Flash and HTML5 ...
May 15, 2017
I’ve identified a demonstrable difference between how a course acts after completing and passing the assessment when running in Flash vs. running in HTML5.
After completing and passing a course with a score of (say) 100% this is what is different:
- In HTML5, any further revisits to any screens prior to exiting the course is not remembered when you relaunch the course – you always come back to the Quiz Results page. [Bad]
- In Flash, any further revisits to any screens prior to exiting the course is remembered when you relaunch the course – you always resume to the screen you exited on. [Good]
- In HTML5, when relaunching and exiting, your previous score percentage is retained (unless you retry the quiz of course). [Good]
- In Flash, when relaunching your previous score percentage is immediately set to 0%, so when exiting again, a score of 0% shows up in SCORM Cloud despite still showing “completed” and “passed”. This can be seen in the SCORM conversation [Bad]
We can demonstrate #1 and #3 in HTML5 mode by repeatedly launching and exiting the course. We can then re-enable Flash and demonstrate #2 and #4 occurring on the next launch.
This has been tested using Google Chrome (with and without Flash enabled) on SCORM 2004 3rd editing. I believe the bug is browser independent and also SCORM 2004 editing independent.
The “not recording any further of progress ” issue in HTML5 happens to stop the issue in #4 above that occurs in Flash but because one bug is stopping anther bug from occurring. I believe the correct process should be to
- continue to maintain and communicate state data back through SCORM after completing the course (unless LMS launches in “review mode” rather than “normal mode”
- do not touch cmi.core.score.raw/min/max unless you complete/retry another assessment.
Personally, I really think Storyline (and Studio) should not even report a new scores until after the user completes all questions of the quiz. This stops you scoring (say) 10% because you happened to retry the quiz and exited after answering just one question. Either the quiz internal state should be discarded upon early exit (saves on additional cmi.suspend_data size), or it’s state is held internally (cmi.suspend_data) until all questions have been answered and the quiz scored at the end. However, this is a separate issue.
As you can understand this is causing real problems with customers who are seeing 0% in their results despite passing the course.