Can Storyline ONLY publish as HTML5?

We are reaching a point within our organization where we are no longer able to offer Flash products. Since that is the default publishing output of Storyline, we are questioning whether we can continue with this software. 

Is it possible to FORCE a course to only open as HTML5? If the story.html file is removed, and the course is launched from the html5 instead, will that have repercussions? 

I'm concerned about only using the html5 output. The quality is slightly degraded, it seems. Suggestions? Advice?

38 Replies
Carolyn Kunz

Hi Krista,

If you only want to launch the HTML5 version of your course, you need to link directly to the story_html5.html file in the output folder.  Not all Storyline interactions/features work in HTML5 so I would suggest that you refer to these pages Storyline 1 or  Storyline 2  during development.  Good luck!

Sjoerd de Vries

There is also a previous discussion around this topic: https://community.articulate.com/discussions/articulate-storyline/storyline-html5-output-only

https://community.articulate.com/discussions/articulate-storyline/can-html5-output-be-delivered-without-any-use-of-flash

Since then we are way further. At Philips, we will abandon flash support from January 2016. No flash is allowed then.

Currently, when I upload a scorm file, it depends of the browser what's displayed. Besides having more freedom, flash suffers from so many security issues that I believe it will be banned by other companies as well.

When our company demands that scorm files may not contain any flash, I hope Storyline will have the option to exclude it. I recently used Adobe Captivate 7 to re-publish some older files and there is just an option to set it separately and a message is displayed which interactions are not supported.

I believe the biggest problem was IE9, which did not properly support HTML5. We don't support IE9 anymore and within a few months IE11 will be our default browser. Therefore we abandon all flash content in 2016.

 

 

Ashley Terwilliger-Pollard

Hi Sjoerd, 

I know there have been a number of discussions about Flash vs. HTML5 recently, and currently our documentation and supported browsers are detailed here.  I like to use a site such as HTML5test.com to see how the different browsers rank and score with using and displaying HTML5 content - and you can use that to look at your current browser set up in addition to the ones we have mentioned in our documentation.

Our team continues to look at adding more supported browsers based on elements such as those seen at that website, and we're also always interested in users feedback so you can share thoughts here in the forums or directly with our product development team here. 

Ashley Terwilliger-Pollard

Hi Alexander,

We don't have an option yet to only publish for HTML5, but many users direct to the story_html5.html link to force the content to display the HTML5 output. As you mentioned, it sounds like you're also modifying the published output - and that may work as well, but it's not something that I can offer assistance for. I'll defer to the community for additional input there, and you will want to confirm that when you're viewing the HTML5 output that you're doing so in a support browser as detailed here. 

Alexander Reid

Ashley,

Can you please assist with Case #00766155?  The Support Engineer is not listening to anything I'm saying and is just replying to me with copy/paste responses.  I have proven on my LMS and with SCORM Cloud that the Flash version of the course does not tabulate results the same way as the HTML5 version.  I need to determine if there's a way to fix this, if not need a correct procedure to block the Flash version from loading on desktops; what I mentioned above did not completely work, it actually garbled up many slides with weird behaviour.

Additionally, this has nothing to do with an LMS as you get the same behaviour by running the local preview in Storyline, which I believe also displays in Flash.

Ashley Terwilliger-Pollard

Hi Alexander,

Sure - let me take a look, so I appreciate that you shared the case number. If you're seeing these results after making the changes to the published output we'll be unable to assist - but if we're able to replicate it using the source (.story file) prior to the changes then that is something we can help with. 

I'll be in touch here shortly. 

Alexander Reid

Just try exactly what I detailed in the original case communication and you'll see the problem right away.  Get the first 5 drag and drops correct (blue shoe, planche, blue shoe, planche, planche), then fail the rest and you'll see a score of 5/20 (correct behaviour).  Retry from the Results page, fail the first 3, and it will give you a score of 1/20 (incorrect behaviour).  This is what happens with the Flash version.

If you run the HTML5 version, you get perfect behaviour: get first 5 correct, fail rest, get score of 5/20.  Retry, fail first three, get 0/20 (correct behaviour).  There's something fishy with either the way the results are being reset in Flash or the way Flash is tracking results as you make your way to the Results page.

Thanks for your assistance, appreciated.

Alexander Reid

The game has a total of 20 questions and allows you to make a maximum of 3 mistakes before it boots you out to the results page, so if you fail the first 3, you should score 0/20.  

With the HTML5 output, you can try any combination of results with retries and it should always score correctly no matter what.  It's only the Flash output that behaves strangely and the best way to see that is to score perfect on the first 5, fail the next 3 to be brought to the results slide where you'll see a score of 5/20, and then if you retry and fail the first 3, it will give a score of 1/20 when it should give 0/20 just like in the HTML5 version.

Mike B.

I think it would be best to correct the flash issue, but if you want to force HTML5 output by modifying your published files, check out the thread below. This is page three, but there is another solution presented by Steve earlier in the thread.

https://community.articulate.com/discussions/articulate-storyline/how-to-force-the-lms-to-call-index_lms_html5-html?page=3

Alexander Reid

Thanks for the procedure, but unfortunately it doesn't work with my LMS.  It ends up merging slides and slide layers in weird ways.  :(

Also, there seems to be a negative impact on scaling.  The browser window opens up pretty small by default, but you can manually scale it to full screen after.

Mike B.

Try Steve's solution on this page then: https://community.articulate.com/discussions/articulate-storyline/how-to-force-the-lms-to-call-index_lms_html5-html?page=2

It is similar to what we use and just involves setting a variable (strContentLocation) within the code that tells it to load story_html5.html instead of story.html. If that doesn't work for you, I can dig out the actual source code that we're using.

Mike B.

Very weird, as it should be using the same mechanism that Storyline itself uses to determine which version to display to the user.

Edit your index_lms.html so that the section that looked like this:

<script>
var g_biOS = (navigator.userAgent.indexOf("AppleWebKit/") > -1 && navigator.userAgent.indexOf("Mobile/") > -1);
var g_bAndroid = (navigator.userAgent.indexOf("Android") > -1);
if ((g_biOS || g_bAndroid) && true)
{
var strLocation = location.href.replace("index_lms", "index_lms_html5");
location.replace(strLocation);
}
</script>

Now looks like this:

<script>
var g_biOS = (navigator.userAgent.indexOf("AppleWebKit/") > -1 && navigator.userAgent.indexOf("Mobile/") > -1);
var g_bAndroid = (navigator.userAgent.indexOf("Android") > -1);
var strLocation = location.href.replace("index_lms", "index_lms_html5");
location.replace(strLocation);
</script>

Let me know if that works.

Alexander Reid

I'm using Google Chrome in OSX.  I get the same slider layer mixups in SCOR Cloud too.

I have support looking at my original problem to determine why the Flash output is tabulating a Quiz section differently than HTML5, hopefully they can assist at that level and then I can leave the default Flash/HTML5 publication.

Ashley Terwilliger-Pollard

Hi Alexander,

Sorry I missed this earlier today - and your updated steps. I figured that out after a few attempts through. ;)

I took a look at your case with Rowie, and it seems he was able to isolate it to one slide that was causing the odd scoring behavior and determined it to be corrupt. Upon removing that slide he shared that the scoring worked normally again - and also that importing it into a new file (a common way to solve corruption) presented the same issues with your course. It seems that you stripped it down further, and are still seeing the same issue so we'll continue to investigate as perhaps something is occurring to the files on your end if Rowie was able to run through it successfully if just that one slide was removed?