Just to clarify, it is actually HTML5 that is not supported well in IE9. Storyline publishes the output, but if someone is using a browser that doesn't have a lot of support for HTML5 then you're going to have issues. A great workaround may be to publish for both Flash and HTML5, and if someone is using IE9 the Flash version should load rather than the HTML5 version.
With that being said, it would be interesting to see if the HTML5shiv would provide a bit more support in IE for HTML5...
Its strange... I did a big project using HTML5 export in storyline 1 which ran perfectly in our target IE9 browser.
I've just started doing a new project for the same client and find that the same file exported to HTML5 via storyline 2 does'nt work - the player never gets beyond the buffering screen. Is it possible that the HTML5 output via storyline2 is less compatible than that created by storyline1? If anyone has had any joy getting HTML5 output from storyline 2 to work in ie9 I would love to hear how you did it.
I have worked with clients before (mainly government) that did not allow the flash player to be installed on computers, so everything I built for them had to be non-flash.
This would be the only logical reason I could think of for not wanting to use the Flash output in IE9...
Apologies for the long response time - yes it's as Brian says - the client does not allow the flash player to be installed on their computers nor flash files to be served on their network.
10 Replies
Just to clarify, it is actually HTML5 that is not supported well in IE9. Storyline publishes the output, but if someone is using a browser that doesn't have a lot of support for HTML5 then you're going to have issues. A great workaround may be to publish for both Flash and HTML5, and if someone is using IE9 the Flash version should load rather than the HTML5 version.
With that being said, it would be interesting to see if the HTML5shiv would provide a bit more support in IE for HTML5...
A couple of good references -
Supported browsers for different outputs - http://www.articulate.com/support/kb_article.php?product=st1&id=4mau4vyvbq4n
Comparing Storyline's Flash, HTML5, and Articulate Mobile Player output - http://www.articulate.com/support/kb_article.php?product=st1&id=1568gg1ayot2
And finally, one of the best resources for browser compatibility with HTML5 - http://html5test.com/
IE9 scores 138 plus 5 bonus points, out of 500 possible points. That's a lot of functionality that will not work in IE9.
As a comparison, Chrome scores 437 plus 13 bonus points, out of a possible 500. Big difference...
Its strange... I did a big project using HTML5 export in storyline 1 which ran perfectly in our target IE9 browser.
I've just started doing a new project for the same client and find that the same file exported to HTML5 via storyline 2 does'nt work - the player never gets beyond the buffering screen. Is it possible that the HTML5 output via storyline2 is less compatible than that created by storyline1? If anyone has had any joy getting HTML5 output from storyline 2 to work in ie9 I would love to hear how you did it.
Hi Lucy!
We do not support the HTML5 output in Internet Explorer. Check out our system requirements for both authoring and viewing here.
Hi Lucy, I'm guessing that your client must have a restriction on using the Flash player? HTML5 and IE9 are not a good combination...
Not to mention that support for IE9 will be ending at the end of 2015 for most modern operating systems.
Out of curiosity, why would you want to use HTML5 instead of the default Flash?
I have worked with clients before (mainly government) that did not allow the flash player to be installed on computers, so everything I built for them had to be non-flash.
This would be the only logical reason I could think of for not wanting to use the Flash output in IE9...
Apologies for the long response time - yes it's as Brian says - the client does not allow the flash player to be installed on their computers nor flash files to be served on their network.
Thanks for sharing Lucy! Hopefully Brian's solutions/suggestions shared above will assist you.
This discussion is closed. You can start a new discussion or contact Articulate Support.