Storyline in HTML5

Eric,

I've found that Chrome, FF, and IE behave differently resizing page elements when the window is resized with CTRL + , CTRL -, CTRL 0.  I recently found that Chrome will completely hide the MENU bar on a website I use frequently if it is resized larger.  No problem in FF or IE.

After this experience, I compare first with normal resolution (CTRL 0), then examine the resizing behavior.  It may be that the issues you observe are more to do with resizing than HTML5.

Sam

Hi Eric,

Please see the link below for more information on distributing your content:

http://www.articulate.com/support/kb_article.php?product=st1&id=9rco1wa3ebjp

In a nutshell, if your browser supports Flash, it's always best to view the content via the Flash Player.  Thus, just link to the story.html file and we'll automagically redirect to the best experience depending upon the device.

I've got more than one client that have requested that we deliver SCORM training on an iPad this year.  The only avenue to do this is via HTML5 (for the iPad).

Many posts in this forum that raise issues with Storyline HTML5 seem to end with suggestions that the author move to Flash or the Articulate Mobile Player, neither of which will solve the problem of providing trackable SCORM courses on an iPad.

I would like to see Articulate apply more development into resolving the missing and broken HTML5 features in the upcoming releases.  HTML5 is the only Storyline format which supports SCORM on the iPad.

Hi Sam,

Thanks for the feedback.  We are certainly going to look at further developing the HTML5 output to have better feature parity between HTML5 and Flash over time.  As a heads up though, some of the limitations of HTML5 on an iPad are limitations of Mobile Safari's implementation of HTML5 (specifically around audio and video) that are difficult if not impossible to workaround.  But yeah, we will continue to develop our HTML5 player to address any issues and add features to make the parity better with the Flash player version.

@Eric - any chance you could share the .story file with me so I could check it out?  If you can upload it to http://files.articulatetest.com/upload I would certainly like to check out the bugs that you mentioned.  Just send me a note with the name of the file once it is uploaded and I'll make sure we log bugs where appropriate.

-Dave

Is there a list of supported/unsupported features of Storyline html5 output?

John, here is a list that covers the comparison between what works in HTML5:

http://www.articulate.com/support/kb_article.php?product=st1&id=1568gg1ayot2

The comparison matrix doesn't mention SCORM support, or the lack of SCORM support in Articulate's iPad Player.  Any idea who updates this page?

Hey Sam,

About middle of the list it mentions:

LMS: Tracking & Reporting

But we don't specifically mention each of the LMS options we report, we will report AICC, SCORM 1.2, SCORM 2004.

I'm not sure if this post belongs in this thread, but I'm finding it to be helpful, so I'll stick with it. I'm having a really weird issue with  one arrow (Articulate arrow) not showing up in html5. It works in the flash version, but not in the other. I might have to save it as an image and reinsert it--any ideas???

Hey Juliette,

Would you mind uploading your .STORY (the source file) project to http://files.articulatetest.com/upload and letting me know the name of the project.  I'll take a look at it and let you know what I find.

-Dave

Dave,

Thanks so much. I was able to recreate the error in a test file, so I uploaded that to the test site for you. The file name is Arrow_test

I'm hoping it's user error on my part

Juliette

Hi Juliette,

Thanks for uploading that.  Yeah, that looks like a bug, I'll see if we can get that fixed.  Saving it as an image and reinserting should workaround the issue for now.

-Dave

Thanks so much, Dave!

I was seeing similar weirdness on the iPad with arrows, some not showing at all, some missing the head, very inconsistent. I am going to try the 'save as an image' solution and hopefully that will work until it gets fixed in Storyline. Thanks for posting this.