Story.html embedded in a web page - IE9, HTML5 issues

We have a course that is embedded in a web page. This works fine for Chrome, Firefox, IE11 and Windows Edge.

When the user tries to launch the course, a few issues can occur:

  • The course does not open in IE9; the user sees a blank screen. 
  • The course does not open in iOS devices. My guess is that the story.html does not run the "sniffer" when it is embedded in another web page.

Has anyone else had this problem and found a solution?

6 Replies
Ashley Terwilliger

Hi Glenn,

How have you embedded it? Are you following the steps here?  When you try to access it in IE9 what occurs? iOS? What iOS version are you using? 

If you'd like to share a link to the course we're also happy to give it a test, and you may also want to look at uploading to another page (feel free to use one of the options here) and see how that works as well. 

Glenn Simsek

Hi Ashley,

It looks like iOS is now working but in IE9 the course still does not open and the user sees a blank white screen. 

The iframe code that our vendor is using is:

<iframe src="" width="100%" height="700" scrolling="no" style="border:none"></iframe>

Do you think that anything in the above could be contributing to the problem?


Ashley Terwilliger

Hi Glenn,

Are you viewing it on Android in the mobile player or in the Chrome browser? When you say cut off , how much are we talking? Do they see the course embedded in the page, is that perhaps how it's being cut off if it's shifted to one side? 

As for the iFrame code, I don't know enough about how that would interact with IE9, but I can't suspect the code would cause issues in that browser alone. Are you using the latest update of Storyline? I know there were some issues with IE in general that were fixed in the latest update so that's worth double checking. 

Ashley Terwilliger

Thanks Glenn for letting us know about the IE9 issue and it being server specific. 

As for the Android issue, it's really difficult to say without seeing it. I don't see any known issues that would match this, so we'd want to take a look at your .story file and if you could let us know where and how you're viewing the content that'll help us track it down further. Can you send your .story file along here?