Storyline and Studio: Here’s Why an HTML5 Course Gets Stuck on the First Slide in Google Chrome

Article Last Updated

This article applies to:

If a Storyline or Studio HTML5 course won’t advance past the first slide when viewed in Google Chrome, it might mean that the server where your course is hosted has an outdated MIME type. If that’s the case, you’ll see 406 errors in Chrome’s developer tools when the course becomes stuck.

The best solution is to ask your server administrator to replace the experimental MIME type of application/x-javascript with the standard MIME type of application/javascript. Then your HTML5 courses will perform correctly.

If your server administrator can’t change the MIME type right away, you should be able to work around it by modifying your published course. Here’s how:

  1. In your published output, open the html5 folder, the lib folder, and then the scripts folder.
  2. Open the slides.min.js file in a text editor, such as Notepad.
  3. Search for "application/javascript" (including the quotes) and replace it with "application/x-javascript".
  4. Save and close the slides.min.js file.
  5. Upload the published output to your server and test it again.

If modifying your published output solves the problem, be sure to make the same change every time you publish a course.