Existing Storyline courses not working in Chrome
Jan 02, 2020
Is anyone else having this problem?
We've discovered that all of the Storyline courses we host on our website have recently stopped working in the Chrome browser (still fine in Firefox, Edge, and IE). I suspect it's a Chrome update not playing nicely again seeing as our courses work everywhere else. I'm looking in Chrome version 79.0.3945.88 on desktop and 78.0.3904.108 on mobile.
The behaviour we're seeing is that the courses load without issue, however when the user presses a 'start' button (which has a trigger to execute some basic javascript for tracking purposes and jump to slide 2.1) the action is not performed and all of the objects on the slide become un-clickable (it seems like the course just freezes up). We're mostly using buttons on the slides themselves rather than the default player buttons, but it also happens with the player buttons.
By opening a course which already had some of my progress saved I was able to ascertain that it doesn't happen on every button throughout our courses, however I did eventually reach a point where the next slide wouldn't load. At this point, there were two common factors with the start buttons mentioned previously. Firstly, it was jumping to a slide in the next scene, whereas the other navigation buttons that were working for me were all just going to the next/previous slide within the same scene. Secondly, the slide it was jumping to is set to execute some javascript when timeline starts.
In terms of output, we publish for Web and place the files on our server, then publish them to our website using Sitecore. As mentioned before the courses do contain a little bit of custom javascript for reporting.
Our courses hosted as SCORM packages on our LMS (Moodle) seem to be unaffected. If I open the file from the browser directly instead of on our website it also works fine.
Based on all this, my gut feeling is that it's something to do with how Chrome's interacting with the javascript. Does anyone know if there's been a change in how Chrome handles this sort of thing?
4 Replies
Hi Tim,
Thanks for reaching out and sorry to hear you're coming across this issue! While we don't support Javascript, I've opened a case on your behalf with our support engineers to see if we can help you pinpoint the issue.
I've shared the details with them, so be on the lookout for a response soon to find the culprit!
Thanks for the response Ren, I'll watch this space!
Hi Tim,
I don't have an answer to your question, but am trying to now talk someone through uploading a published-to-web output from storyline in SiteCore (which I have never used) - do you have quick steps you'd be willing to share for for how to do that?
Hi Sally,
Afraid I can't give you much in the way of specifics because there was a lot of initial setup done in our sitecore which has been renamed and structured to our website and organisation terminology, so I'm not sure what it looks like for other people. But the general basic things to do (at least the way we do it) are to publish the Storyline file for Web and then host the output on their web server, and then they'll need to point the sitecore entry to the url location of the story.html file. Hope that's of some help!
This discussion is closed. You can start a new discussion or contact Articulate Support.