Problems with HTML5 output and LMS
Apologies in advance for the length of this post, but I'm trying to be thorough.
I've just run a battery of LMS tests with a six-slide Storyline course. The course, if this matters, was imported from Studio and then modified in Storyline. The summary is that saving and restoring works properly in every desktop browser I've tested, using the Flash-based output, but saving fails using the HTML5 output on the iPad, Safari and both the PC and Mac versions of Chrome. These tests were all run inside our home-grown LMS, which has been online for years (and which, I will admit, is not perfect, and I suppose could be the source of the problems, but that's not what the evidence suggests at present).
I ran the following tests:
1. Launch unstarted course, complete course in one session
2. Launch unstarted course, stop halfway through, then resume to the end in the same browser
3. Launch unstarted course in one browser, stop halfway through, then resume on another browser to the end
I tested using Safari6, Chrome23, Firefox16 on OSX Mountain Lion, IE9 and Chrome23 on Windows7, and IE7 on XP. I also ran Mobile Safari on a third generation iPad running iOS6. I launch all courses in a new window from the LMS. "Completion" in my course is determined by # of slides viewed--for this test, 6 out of 6 tests. Course was published using SCORM2004, version 2.
TEST 1: All Storyline output formats, browsers and devices passed this test. That is, in any of the above configurations, if you started a course anew, and completed it in a single session, state was properly tracked back to the LMS. More specifically, an LMSCommit() command was fired back to the LMS when the last slide loaded, and that command told the LMS that the course was complete.
TEST 2: The combination of desktop browsers + Storyline Flash output passed this test. All browsers tested against the HTML5 output, however (iPad, Safari6 and Chrome23) failed this test. More specifically, the course launched properly the first time, saved properly at the end of the first session (by just closing the browser window), and then restored to the proper slide when the second session was launched. I was able to continue on to the last slide of the course during the second session, but once I hit the last slide of the course, no LMSCommit command was fired back to the server. Moreover, if I closed the course window, an LMSCommit command was fired off to the server, but that command did not say the course was completed.
3. This worked in all cases, except if the course was restored to the HTML5 version of the course, in which case it behaves just like case #2, above. For example, I could launch the course on the iPad, quit, then resume on IE9 to the end, and the course would mark complete. However, if I started the course on IE9, then resumed on the iPad, it would restore to the right slide, but the course would not mark complete. Just to make sure this problem wasn't limited to the iPad, I launched the HTML5 version in both Safari and Chrome, and witnessed the same behavior.
So it seems like something is wrong with the way the HTML5 version is "counting slides", at least on restores? Has anybody else encountered this? Obviously, this is a show-stopper, so I'm certainly hoping that I'm just doing something wrong.
Also, and I don't know if this is relevant, but just in case, any time I launch a previously unlaunched enrollment with the HTML5 version, I see this screen first:
The title of the course appears above the "Play" button, and an image of the first slide appears to the right, but I've removed those for privacy issues. So I have no idea if this screen is related in any way to the issues I'm seeing, but I'd sure like to not have this slide appear. Any way to make that happen?
Thanks in advance,