Storyline has Excellent Html5 support. Although it might not work for every project you've made, if you check the html5 publish option, you will get a file called story_html5.html. If you target this or rename it as your index.html you might be surprised at how well pure html5 works for you.
Storyline publishes a collection of files and it'll include SWF files. I know some users have mentioned deleting them and point directly to the story_html5.html file as Richard mentioned above - but it's not something I'd recommend or that we could support in terms of the SWF files being removed. If you want to ensure your users see the HTML5 output - pointing directly too it using that link is something that has worked well - but you'll still want to have all the files within the published output folder uploaded to your web server/lms or downloaded locally (depending on how you published). It's also worth noting that there are more limited browser options for HTML5 content as detailed here.
Hi Ashley, Sorry about that, I didn't intend to imply to remove any of the swfs. However, I did note on the link you provided (and staff recommendations on the forum) that Firefox is not mentioned for HTML5, and I wanted to point out that it not only works fairly well, but in fact it's the only browser that works where all the files(html5 or swf) don't have to be placed on a server to test linkages etc..
No worries - I know users delete the swf files and report it works fine, just not something I can back or support. :)
As far as the HTML5 output, our team continues to test different browsers and updates and based on that detail the browsers we support. I've seen a lot of users mention that they've tested their content in Firefox and all works well for them - so they continue using it. I personally like to use a site such as HTML5test.com to see how different browsers fare in terms of their "html5 score".
As far as testing it locally, that is likely due to the browser and flash security issues on testing web content locally. You can read a bit more about that here and we always recommend uploading to the intended environment to test properly.
5 Replies
Storyline has Excellent Html5 support. Although it might not work for every project you've made, if you check the html5 publish option, you will get a file called story_html5.html. If you target this or rename it as your index.html you might be surprised at how well pure html5 works for you.
Hi Eric,
Storyline publishes a collection of files and it'll include SWF files. I know some users have mentioned deleting them and point directly to the story_html5.html file as Richard mentioned above - but it's not something I'd recommend or that we could support in terms of the SWF files being removed. If you want to ensure your users see the HTML5 output - pointing directly too it using that link is something that has worked well - but you'll still want to have all the files within the published output folder uploaded to your web server/lms or downloaded locally (depending on how you published). It's also worth noting that there are more limited browser options for HTML5 content as detailed here.
thank you both for the responses!
Hi Ashley, Sorry about that, I didn't intend to imply to remove any of the swfs. However, I did note on the link you provided (and staff recommendations on the forum) that Firefox is not mentioned for HTML5, and I wanted to point out that it not only works fairly well, but in fact it's the only browser that works where all the files(html5 or swf) don't have to be placed on a server to test linkages etc..
Hi Richard,
No worries - I know users delete the swf files and report it works fine, just not something I can back or support. :)
As far as the HTML5 output, our team continues to test different browsers and updates and based on that detail the browsers we support. I've seen a lot of users mention that they've tested their content in Firefox and all works well for them - so they continue using it. I personally like to use a site such as HTML5test.com to see how different browsers fare in terms of their "html5 score".
As far as testing it locally, that is likely due to the browser and flash security issues on testing web content locally. You can read a bit more about that here and we always recommend uploading to the intended environment to test properly.
This discussion is closed. You can start a new discussion or contact Articulate Support.