Windows 10 IE Edge and Storyline 2.0 Support

Sep 10, 2015

Hi All, 

We develop a lot of courses using Articulate Storyline, with Windows 10 coming into the scenario and Microsoft sending out a message to all Enterprises to move their applications to IE11 Enterprise Mode. It will greatly impact the way we developed and design our courses. 

I would like to know the following from Storyline team:

  1. When do we get a SDK for Storyline 2.0 so that we can customize the content as per our requirement. 
  2. How can we customize the Storyline Skin to support only HTML5 and not have frame.swf as the skin. 
  3. What are the plans of Articulate to move into only HTML5 platform seeing the way Apple, Google and Microsoft now restricting the Flash Active-X components in their browsers?

Thanks and Regards,

Irfan Kazi

 

13 Replies
Ashley Terwilliger-Pollard

Hi  Irfan,

There is a Storyline 2 SDK available, but it's only for Flash output. 

You can author and view Articulate Storyline 2 courses on Windows 10 computers. If you're prompted to reactivate Storyline after upgrading to Windows 10, see this article for instructions. You can also view the output in the following browsers. 

As for the future, we have a dedicated team focused on HTML5 as well as dedicated teams focused on playback via the Articulate Mobile Player. While we can't speak to future releases, we are aware of the decisions being made that impact the ability of web browsers to display Flash content and are actively working to make sure that our content will work on all major web browsers. 

Ashley Terwilliger-Pollard

Hi Willi,

Was there a specific piece you were looking for an update on? Storyline 2 still does not offer support for HTML5 in IE or the Edge browser. Storyline 360 and Rise, both as a part of the Articulate 360 suite of tools offer a lot more HTML5 options such as variety of browsers supported and ability to publish for HTML5 only, and with Rise fully responsive output and in Storyline a new responsive player. 

Ashley Terwilliger-Pollard

Hi Tasha,

I hope we're not to that point yet - as we'd want to give your course a test as well to spot anything else that may be happening! Are you able to share a copy of the .story file with us? You can upload it here using the "add attachment" button or send it along to our Support Engineers here! Either way we can take a look at publishing it, uploading it to some test sites and trying it out in a few different browsers. 

Also, just a reminder that when you reply via email it'll include your signature in the response. You can edit the post to remove that if you don't want it in the public forum. 

Tasha Rosenbaum

Thank you for the follow up. I am unable to send you the file, that being said I am using the publish for Web, and have checked the option for HTML 5 output. On the Edge browser the user is unable to interact with the click and hover interactions in the module. I hope that can help the engineers. I have read through a few other forum posts and I see that this is a common error with Storyline 2 publishes and Edge. 

Ashley Terwilliger-Pollard

Hi Tasha, 

Were you able to confirm if the Flash was working once uploaded to your web server? The link would look like story.html vs story_html5.html at the end. The latter link would indicate it's the HTML5 content which wasn't supported in IE11 or the Edge browser with Storyline 2.  

If you were testing it locally that could also cause issues with the playback, and specifically with Flash as detailed here. 

Let us know if you need any other assistance, and our Support Engineers are able to sign an NDA when reviewing content, so everything is kept confidential and private to our staff.

Thomas Dinwoody

We are recently up grading to the Windws 10 platform as well and this issue has now started to appear for us as well. Course was developped on SL2  where users can click on one of the interactions to view a specific layer but when they return back to the base layer they can not click any other interactions. Any suggestions would be appreciated!

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