SCORM's is not working well on Google Chrome

Hi folks!

After the latest Google Chrome patch (72.0.3626.119 version), every SCORM is showing issues when I scale the player to fill browser window. The slide elements is disappearing or changing order. For example: background images above the captions.

The attached images shows the preview on Storyline, the presentation in ScormCloud scaling the player to fill browser window and a third image in ScormCloud as well, but on original size. Can see the difference?

If necessary, you guys can test the same SCORM by yourselves:
https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=8f0e465c-5d79-430f-8ef2-315280b0edde

Please, I really need help to solve this issue. Thanks in advance!

5 Replies
Alyssa Gomez

Sorry you're running into that issue, Rodrigo! Are you using Storyline 3?

Chrome recently implemented a change in update 72 that is causing slide objects and player tabs to be incorrectly hidden. Specifically, this happens when viewing the course in a large browser window. Reducing the size of the window should bring the resources tab back into view. You can also republish the content using the "Lock player at optimal size" setting. 

While this has already been fixed in Storyline 360, we're adding an enhancement to Storyline 3 in the next update that will resolve the issue you're seeing. Stay tuned, that update is coming soon!

Leslie McKerchie

Hi Rodrigo,

I'm happy to share that an update to Storyline 3 is available today.

Enhanced: We added support for Google Chrome 72 and Safari 12.0.3. If objects disappear when viewing a course in these browsers, install the latest Storyline 3 update and republish your course.

Check out all the details on the latest release here.

Please let us know if you run into any issue after updating and republishing.

Ashley Terwilliger

Hi Crystal,

What update of Storyline 360 are you using? The latest update is Storyline 360, build 3.26.18364.0 and should resolve this issue. If you're still running into it, can we take a look at one of your .story files to continue testing and troubleshooting? You can share it with our Support Team