HTML5 Interactions not Working on iPad

falcon44nkc Community Member Posts: 90
I am creating interactive simulations in Captivate and publishing as HTML5. These simulations play fine on the computer but don't work on the iPad. I’m confused because they have worked on the iPad in the past.

I’ve tried both as an HTML5 extension and as a web window.

For HTML5 extension, here’s what I do to publish: In Captivate I publish as HTML5. In Lecora I use an HTML extension and bring in the HTML5 folder by clicking on additional files. I then use the Edit option to add this code: <iframe src="Download/index.html" width='946' height='609' frameborder='0' scrolling="no"></iframe> (for example)

This has worked for years and now suddenly it doesn’t. I first encountered this using Lectora 17 and was advised there was an issue with 17. So I went back to 16 and it worked. But now it doesn’t work in 16 either. On the iPad, a play button appears but if you click it the first page of the simulation appears but the play button doesn’t go away and you are unable to click on the button in the simulation.  Then from there is it just generally messed up.

I have Lecora 17.1 and Lectora 16.2.2.

Any help is greatly appreciated.

Thank you!


  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    When publishing make sure 'Seamless play' is unchecked. Lectora 17 Seamless play publishes in an iFrame and you need to make sure scripts and everything else targets the correct content. Disabling Seamless Play makes it work as was in Lectora 16.

    @Trivantis - Wouldn't it be good to create warnings for elements targeting non-existing frames when publishing with 'Seamless' on ? This issue comes around and around time after time.

    Kind regards,


    Mmm... the fact it doesnot work in 16 puzzles me. Might be a Ipad issue. If you share a sample some helpfull soul here might check it out.
  • falcon44nkc
    falcon44nkc Community Member Posts: 90
    Thanks. I gave this a try but unfortunately there is no difference. I didn't see the Seamless Play option in Lectora 16 but it was there in 17. I unchecked it but there is no difference in the HTML5 playback on the iPad. Thank you for the suggestion, though.

    Any other ideas?
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    If you can share a sample of your title, i can check it.
    Noticing quite a few changes in 17.1  on the mediaparts in Lectora though...i havenot yet updated , running 17.06.
    So that might be causing issues with 17.1 vs. 17.06
  • falcon44nkc
    falcon44nkc Community Member Posts: 90
    Sorry for the delay: I replied earlier but I see now that my message didn't go through. I think the file size was too large.

    The title was rather long so I made a copy of it and deleted all the other pages. Attached is the zip file.

    On the page Accessing the Floor Plan there are two buttons - "HTML5" and "WebWindow" - which takes you to the two different ways I've tried.  This is the Lectora 16 version.

    Please let me know if I can provide any additioanl information.

    I really appreciate your help!
  • falcon44nkc
    falcon44nkc Community Member Posts: 90
    Update: This still isn't working on the Ipad. I just tested it on an Android tablet and it DOES work on that device (both using HTML Extension and a Web Window).

    What could be differnt on the iPad to prevent the simulations to work?
  • dfleary
    dfleary Community Member Posts: 82 ☆ Roadie ☆
    With Lectora v17 there are some changes that may need to be made to your scripting in order for it to work properly with Seamless Play Publishing. Perhaps the following will help:

    Scripting Limitation/Modifications with Seamless Play
    • All scripting technically works but if they add their own HTML elements through scripting they should use the function that we have provided which will work in Seamless publishing and non-Seamless cases.  The functions are:
      • getDisplayWindow()
        • Returns the window objects that is to be used for dealing with the js objects generated by lectora and all window related attributes
      • getDisplayDocument()
        • Returns the document object that is to be used for dealing with the visual HTML objects, it contains all of the currently HTML elements for the page
      • GetCurrentPageDiv()
        • Returns an HTML element that represents the page div
      • GetCurrentPageID()
        • Returns a string with the name of the current page div
      • appendElement(obj, parentElement, htmlElement)
        • This function can be used for attaching objects to the current page div; the customer would only need to pass in the last attribute as either a HTML element or a string.