I am having serious issues with publishing courses to HTML5 with Storyline 360. Microsoft Edge just crashes when I try to run a course on the LMS or on the web. It won't go past the first page of the course before it crashes. On Chrome and Firefox, I get a flashing between slides but the course just completely breaks when I try to load it on Edge.
None of the above issues occur when published in Flash and I have opened a case for the flashing screen problem. Is anyone else encountering similar issues with Edge when publishing Storyline 360 courses in HTML5?
I noticed you were working through this issue with Angelo in your case, and I reached out to him about the problem you're having in Edge. He is going to follow up with you to let you know what he found in his testing.
I'll continue to follow along with your case and share updates here!
Are you also using the Edge browser? Have you made sure you're on the latest update of Storyline 360 as well? Is this a recently published course to your LMS, or one you've had uploaded there for awhile?
I'm sorry for the issues you both ran into with Chrome playback of Storyline courses, and I also saw Gillian reached out here. I wanted to share my latest response here for anyone else who may come across this discussion:
Our team has seen with the recent Chrome updates that local playback of content does not work. This would only be for Storyline 3 or 360 content that you had published for Web or LMS and were playing back while housed locally such as on your C drive.
If you've uploaded your courses to the web server or LMS, the playback there should not be effected. If you are seeing issues once you upload to the intended environment as we recommend I'd look at testing outside your environment to narrow down where the issue is. For example:
For web published content you could use Amazon S3 or upload to Tempshare
For LMS published content, take a look at testing in SCORM Cloud.
If you need any other help, let me know! Gillian, feel free to keep the conversation going in your other discussion as well!
Are there any further updates on these Edge issues with 360? I've been using the lasted Storyline 360 version, publishing both in flash and html5, and certain pages just seem to crash Edge completely without warning yet function fine in Chrome or FF. Any help appreciated.
Sorry to hear that you've run into an issue viewing your course in Edge.
Curious if the slides that are causing the crash have markers on them? We are aware of an issue related to this and I will add this thread to the report as we track user impact if confirmed.
I have 12 courses that have markers throughout. The markers are now not working with Edge. I am running the latest version of SL3. Is there a workaround for the marker issue?
What Update of Storyline 360 are you using? I'd want to make sure you're on the latest version, available which is update 16.
Just launch the Articulate 360 desktop app on your computer and look for the Update button for the whole tray, and then specifically Storyline. Details here.
If you're on the latest update, can you share a copy of your project file? The issue with markers crashing in Edge is not something our team has been able to replicate consistently, so it'd help to have additional projects.
Given the issues with Edge, and the possibility of publishing with Flash/HTML5 Backup, how will this affect us after browsers stop supporting Flash? Would they just default to HTML5 or would we need to republish? I know that it should automatically switch, but has this already been tested by the Articulate team?
That's right, Joseph! If a browser stops supporting Flash, or if you manually turn off Flash in the browser, the output will default to HTML5. No need to republish!
I'm just curious if there has been some coordination with Microsoft on this - it seems as if after Flash is not supported anymore that this workaround won't work. Will we have to have our users work with other browsers?
I'm not sure which workaround you're referring to? When Flash is no longer supported, if you've published for HTML5 your content will default to that in the browser. Our team is consistently working to improve that HTML5 experience across browsers so that you wouldn't need to switch browsers but just stay on the latest version of the supported browsers.
16 Replies
Hi there Derek, thanks for reaching out!
I noticed you were working through this issue with Angelo in your case, and I reached out to him about the problem you're having in Edge. He is going to follow up with you to let you know what he found in his testing.
I'll continue to follow along with your case and share updates here!
Any updates to provide on this as this issue is happening with one of my courses in LMS. Only with Windows 10
Hi Hugh,
Are you also using the Edge browser? Have you made sure you're on the latest update of Storyline 360 as well? Is this a recently published course to your LMS, or one you've had uploaded there for awhile?
This post was removed by the author
We had similar issue. Change to flash/html fallback and have not had any since.
Get Outlook for iOS
This post was removed by the author
Hi Gillian and Hugh,
I'm sorry for the issues you both ran into with Chrome playback of Storyline courses, and I also saw Gillian reached out here. I wanted to share my latest response here for anyone else who may come across this discussion:
Our team has seen with the recent Chrome updates that local playback of content does not work. This would only be for Storyline 3 or 360 content that you had published for Web or LMS and were playing back while housed locally such as on your C drive.
If you've uploaded your courses to the web server or LMS, the playback there should not be effected. If you are seeing issues once you upload to the intended environment as we recommend I'd look at testing outside your environment to narrow down where the issue is. For example:
If you need any other help, let me know! Gillian, feel free to keep the conversation going in your other discussion as well!
This post was removed by the author
Thanks for sharing Gillian - I will add these notes to your case.
Are there any further updates on these Edge issues with 360? I've been using the lasted Storyline 360 version, publishing both in flash and html5, and certain pages just seem to crash Edge completely without warning yet function fine in Chrome or FF. Any help appreciated.
Hi Robert and welcome to E-Learning Heroes :)
Sorry to hear that you've run into an issue viewing your course in Edge.
Curious if the slides that are causing the crash have markers on them? We are aware of an issue related to this and I will add this thread to the report as we track user impact if confirmed.
I have 12 courses that have markers throughout. The markers are now not working with Edge. I am running the latest version of SL3. Is there a workaround for the marker issue?
This post was removed by a moderator
Hi Fraser,
What Update of Storyline 360 are you using? I'd want to make sure you're on the latest version, available which is update 16.
Just launch the Articulate 360 desktop app on your computer and look for the Update button for the whole tray, and then specifically Storyline. Details here.
If you're on the latest update, can you share a copy of your project file? The issue with markers crashing in Edge is not something our team has been able to replicate consistently, so it'd help to have additional projects.
I'm using the latest version of SL3
Thanks, Fraser. We also do have this reported for Storyline 3 and I'd love to take a look at one of your Storyline 3 files as well.
Let me know if you can share here, or if you'd prefer to share privately.
Given the issues with Edge, and the possibility of publishing with Flash/HTML5 Backup, how will this affect us after browsers stop supporting Flash? Would they just default to HTML5 or would we need to republish? I know that it should automatically switch, but has this already been tested by the Articulate team?
That's right, Joseph! If a browser stops supporting Flash, or if you manually turn off Flash in the browser, the output will default to HTML5. No need to republish!
We're staying ahead of the game to prepare for Adobe's Flash phase-out--you can read more about what we're doing to prepare here!
I'm just curious if there has been some coordination with Microsoft on this - it seems as if after Flash is not supported anymore that this workaround won't work. Will we have to have our users work with other browsers?
Hi Joseph,
I'm not sure which workaround you're referring to? When Flash is no longer supported, if you've published for HTML5 your content will default to that in the browser. Our team is consistently working to improve that HTML5 experience across browsers so that you wouldn't need to switch browsers but just stay on the latest version of the supported browsers.
This discussion is closed. You can start a new discussion or contact Articulate Support.