Working with Captivate Web Objects in Storyline on iPads
Jul 14, 2015
We inherited a project where we have to link to a Captivate 8 output using a web object that pops up in a new window in Storyline. We have to do it this way, of course it would have been preferable to use a Storyline screen capture. The problem I am having is that the Captivate movie is not detecting that it is being viewed on an iPad and is trying to show the swf version instead of the HTML 5. I have tried it with the usual index.html file & I have tried it by changing the name of the multiscreen.html file to index.html, after deleting the original index.html file. Does anyone have any suggestions? I feel like the web object is interfering. When I used a Captivate that was pure HTML5, it worked fine. The product has to work in as many browsers and devices as possible.
6 Replies
Hi Joshua,
I don't know much about Captivate, but how are you linking to it as a web object? Is it hosted on a server somewhere? I know for example Storyline has a difficult time determining to show the Engage content embedded when trying to view an HTML5 output - as it's unable to read the Engage HTML5 code - so instead you have to insert it as described here.
I used the method described in your link:
Go to the Insert tab on the ribbon and click Web Object.
Click the Open Folder button at the right end of the Address field.
Browse to the folder that contains your published interaction and click OK.
Click OK again to insert your web object.
Hi Joshua,
The only other documentation we have is here in relation to inserting Captivate content - but it also says use it was a web object.
I just got it working by embedding the Captivate movie as a hyperlink. I would like to have done it so that the movie was imported in with module's files. Now I have to have a web object that brings the link in from an unsecured server. I don't understand why the Articulate program is stopping the browser detection scripts from working.
But thank you, Ashley, for trying to help.
Hi Joshua,
I suspect it's the same as with Engage - when added following the normal import process the code in terms of showing Flash vs. an HTML5 output is no longer accessible - and as such if you embed as a web object, than it is referencing the original publish location which is able to determine the browser detection and show the correct output. Since it's Captivate I can't say with any certainty that it's the same thing - but that is my best guess.
This discussion is closed. You can start a new discussion or contact Articulate Support.