Microsoft Edge compatibility on HTML5 output and miscellaneous project-crashing bug.
Nov 23, 2016
Hi,
I'm currently doing QA for a project made in storyline.
For the moment, we are trying to avoid using the flash output, but the display on microsoft edge seems to be problematic with HTML5. Some objects aren't placed the same, drag and drop 'hitboxes' (sorry for lack of a better term) are n0t directly on the object, and we get a bug that happens often on edge and less often (but still happens) on other browsers.
I know that html 5 output on windows is only officialy supported with chrome, that is why it is interesting that the last bug I mentionned happens sometimes in google's browser. It appears that the project attemps to load an image that he can't find, which causes the whole project to crash and show a white screen.
I'm unable to display what it is trying to load inside the console. Please note that the project is hosted on a domain.
Would switching to storyline 360 give a better html5 compatibility with other browsers?
Is there a way to see what the browser is attempting to load before crashing?
I know this a big post, you don't need to answer the whole thing I just need a starting point, so if you have some ideas let me know.
Thanks alot,
Nic L.
*Edit:
After further investigations, it would appear that the bug mentioned above is occuring frequently on safari desktop.
1 Reply
Hey Nicolas,
Thanks for taking the time to detail your investigation process so thoroughly here. In Storyline 2, HTML5 output is limited to these browsers:
Microsoft Edge isn't included which is why you're experiencing some erratic behavior there. I would recommend linking to the story.html file as described in Step 6 over here. If you've checked the option to include the HTML5 output, the browser should automatically decide whether to run the html or HTML5 based on compatibility.
That being said, Safari is supported for HTML5 so it concerns me that you're seeing strange behavior there as well. When you're testing in Safari, is this after you've already loaded the content to your domain? If you're testing locally, that could cause some undesirable behavior so you'll want to make sure the content is uploaded to the web before viewing it. It's also important to keep in mind that although the browser may be supported, there are also some features that are not supported in the HTML5 output which you can check out in this comparison sheet.
To answer your question regarding Storyline 360, we do have added browser support for HTML5 viewing and also the option to publish purely the HTML5 content without Flash if desired which you can read more about in Step 3 of this tutorial. Here's the supported browsers for HTML5 content in Storyline 360:
They're also listed in the Viewing Content section of the Storyline 360 System Requirements which you may find helpful to take a glance at. In addition, there are more features now supported in HTML5 for Storyline 360.
Hope that was helpful as a jumping point, please let me know if I can help clarify further or provide any more assistance! :)
This discussion is closed. You can start a new discussion or contact Articulate Support.