Html/html5 output dont play in the latest chrome browser

Feb 09, 2018


Since few days I am noticing that none of my html5/html output run in the latest version of Chrome browser (64.0..). 

It now plays only in the older versions.



34 Replies
Cheryl Powers

we had recently updated all of our articulate 360 products.  We have two new courses that were published for the SAP SuccessFactors LMS in html5.  the two courses would not follow any navigation preventing all forward/backward or selection from learner unless they were using IE.  On a desktop in chrome, it would not advance past first slide and produce the gray spinning wheel.  On an android mobile device, none of the navigation buttons worked, and you couldn't move past the first slide from within the SuccessFactors LMS mobile application.   We spent a week testing every android and chrome scenario.  We reported the issues to both Articulate and SuccessFactors LMS.  Although the courses run in the scorm cloud in chrome. they do not work when published as html for the LMS  in chrome browser whether it's a pc or mobile.  The two courses do not work on SuccessFactors Mobile App on our android mobile devices, but they do work in the SuccessFactors LMS mobile app on an IOS ipad or iphone.  The only way they worked on the android mobile was to bypass the SuccessFactors mobile app, and  instead, use Firefox to launch the LMS via the browser.  We spent another week trying to redevelop the two courses in Rise -which doesn't allow for audio and most of the built-in interaction we had in the original courses.  We spent days recording our screens in storyline preview mode and incorporating the video into the new Rise course.  The LMS doesn't recognize where embedded video leaves off so you have to start any of the blocks over if you can't finish.  It's an awful compromise of quality and doesn't allow for the original interactions for the learner.   We do not control or have direct access to our icontent server that houses our content for the LMS.  so we have raised an issue with SucessFactors too but have had no response yet.

Ashley Terwilliger-Pollard

Hi Cheryl,

I'm sorry for all the trouble you've run into.

I took a look to see if I could find your Support case on this, and I didn't see anything recent. I know how confusing it can be when something works in one location and not another, but working in SCORM Cloud is a great standard and baseline to refer to. As for the SuccessFactors app (or any specific LMS mobile app) we don't support those, as they likely don't adhere to the browser standards of Safari, Chrome, etc. All Articulate content is designed to playback in the mobile browsers and devices detailed here. 

If you heard back from the SuccessFactors team, and you're able to share here, I'm certain others in the community would appreciate an update. I know it's an LMS that a few other folks have run into some odd issues with, so the more information the better. 

Emma Crossley

I have several courses produced a year ago with SL360 and published to the Web (Not LMS). They will now not load..just spinning wheel...this happened on Chrome 65 and now 66..Also on Firefox. They do play in Chrome Incognito and Microsoft Edge.

To be clear this is not the local playing issue recently addressed in an update..these courses are live and now not usable...this is very disconcerting...I assume others are like me who don't have the bandwidth to republish old courses...please tell me there is some fix.

Ashley Terwilliger-Pollard

Hi all, 

We added support for Chrome 66 in the April 26, 2018 update for Storyline 360 and Studio 360. Just install the latest software update and republish your course. 

We're working on a solution for our perpetual apps and will update this article with details as soon as possible. In the meantime, ask learners to use a different browser, such as Firefox, Internet Explorer, or Safari.

Emma Crossley

I see that as of today April 26th there is a SL 360 update that addresses the Chrome 66 issue. I am curious what exactly the fix was?

I am concerned that if it is some sort of workaround that Chrome will come back and release another version negating this work around and on and on and on.

After all, if Storyline has a way to bypass it, so would other less "puritanical" video providers (ie digital advertisers)...and Google would want to combat that.

This discussion is closed. You can start a new discussion or contact Articulate Support.