Chrome and Storyline

Jun 08, 2017

Sandra Karlovich
By Sandra Karlovich

HI, I'm hoping someone can help me.

 

Users in my organization have recently upgraded their Chrome from version 58.0.3029.110 to 59.0.3071.86 and I have been experiencing issues with the elearning modules.  I am observing the following:

 -          Browser opens /story_html5.html by default instead of /story.html file

-         Although /story_html5 file doesn’t exists in the path for some of the modules, browser still opens this file by default and now user sees ‘not found’.

-        story.html works but for some reason, Chrome doesn't open it.

I'm not familiar with html5 but it is causing issues.

Has anyone experienced this before?

Thank you,

Sandra

2 Replies
Brian Dennis
almost 7 years ago06/08/17 at 4:36 pm (UTC)

Chrome is HTML5 so the Storyline published project will defer to the HTML5 story version automatically if the browser supports it. And newer versions of Chrome are phasing out Flash very quickly. I would suggest republishing your projects in SL to have the correct story_html5.html file be created if possible. Good luck

Ashley Terwilliger-Pollard
almost 7 years ago06/09/17 at 8:58 pm (UTC)

Hi Sandra,

Google introduced a new security feature in Chrome 56 that blocks Flash content unless you give it permission to play. As a result, Google Chrome may instruct you to Right-click to run Adobe Flash Player when you launch Storyline and Studio courses.

Here are a couple ways learners can handle this new security feature if you've already distributed a Storyline or Studio course:

  • They can follow the instructions to right-click the screen and allow the Flash content to run.
  • They can view the course in a different browser, such as Firefox or Internet Explorer.

And here are a couple ways you can help learners avoid the issue altogether. 

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