Storyline 2 still allows for you to publish with Flash and host your content on your web server or LMS. You'll want to confirm that users are accessing the course through a supported Flash browser which are documented here.
Also, since we heard from a number of customers that they were being pushed towards HTML5 only output, we built that into Storyline 360, which is a part of the Articulate 360 suite of tools. You can read a bit more about how you choose that and allow for HTML5 only (or first) output.
Thanks for the update. After looking at the Articulate documentation, flash is supported by Google Chrome's latest version. My question is given that Chrome plans to phase out flash based objects as of Feb 2017, won't this affect the storyline projects?
I know you can allow flash but this can be confusing for a lot of users.
If you had included the HTML5 output - that should be served up to customers in Chrome if Flash is disabled. As for what happens come February, I wish I had a crystal ball to say exactly how it would behave - but if I did have one, I'd be using it for better things than Chrome prophecies. ;-) I suspect it would continue to behave as it has when you have Flash disabled on an individual browser basis.
Just an update on this thread: Chrome has stopped Flash from playing automatically. At this point users have to Allow both Flash and JAvascript in their settings to view modules made in Articulate Storyline 2.
I will need to explore additional options for this. I don't know if 360 alleviates this problem or not.
360 does solve this problem - as you can publish for HTML5 only. Take a look at this article on other ways to deal with Chrome blocking Flash, and what we're doing to prepare for a Flash free future.
5 Replies
Hi Aisha,
Storyline 2 still allows for you to publish with Flash and host your content on your web server or LMS. You'll want to confirm that users are accessing the course through a supported Flash browser which are documented here.
Also, since we heard from a number of customers that they were being pushed towards HTML5 only output, we built that into Storyline 360, which is a part of the Articulate 360 suite of tools. You can read a bit more about how you choose that and allow for HTML5 only (or first) output.
Hi Ashley,
Thanks for the update. After looking at the Articulate documentation, flash is supported by Google Chrome's latest version. My question is given that Chrome plans to phase out flash based objects as of Feb 2017, won't this affect the storyline projects?
I know you can allow flash but this can be confusing for a lot of users.
Hi Aisha,
If you had included the HTML5 output - that should be served up to customers in Chrome if Flash is disabled. As for what happens come February, I wish I had a crystal ball to say exactly how it would behave - but if I did have one, I'd be using it for better things than Chrome prophecies. ;-) I suspect it would continue to behave as it has when you have Flash disabled on an individual browser basis.
Just an update on this thread: Chrome has stopped Flash from playing automatically. At this point users have to Allow both Flash and JAvascript in their settings to view modules made in Articulate Storyline 2.
I will need to explore additional options for this. I don't know if 360 alleviates this problem or not.
Hi Aisha,
360 does solve this problem - as you can publish for HTML5 only. Take a look at this article on other ways to deal with Chrome blocking Flash, and what we're doing to prepare for a Flash free future.
This discussion is closed. You can start a new discussion or contact Articulate Support.