Skip to main content
Inspiring
January 7, 2016
Answered

Captivate 9 Widgets are not HTML5 Compatible am Using Responsive Project and Widgets Work in Firefox not IE 11

  • January 7, 2016
  • 2 replies
  • 3755 views

Hello,

I have Captivate 9 and I am using the built-in Captivate widgets (not the ones via Assets). I have created my project as a Responsive Project to be able to view in tablets. Captivate told me the widgets are not HTML5 compatible. When I publish to my LMS, I can see the widgets and interact with the course on my laptop via Firefox, but I cannot see the widgets at all in IE 11. Is there a way around this, or do I need to tell my people to download a different browser to use my course?

    This topic has been closed for replies.
    Correct answer RodWard

    You do not need to create a project as Responsive simply to have it play on tablets or mobile devices.

    If the widgets are known to be NOT HTML5 compatible, best not to use them at all.  IE11 will usually work with Captivate's HTML5 output, but your widgets are probably not going to work in this case.

    2 replies

    Participating Frequently
    January 28, 2017

    Hi!

    I am having the same issue - did you get this figured out?  When I preview my project, I have a Zoom widget (selected from the learning interactions tab) and another accordion button widget (same learning interaction) and when I publish (with the eventual plan of adding to my LMS - Blackboard, the widget disappears.

    Any advice is appreciated! I'm a professor of nursing, and not as tech savvy as most people on these forums.

    Thank-you

    Keri

    Participant
    December 14, 2019

    Hello, I am using the Timer built-in widget and the Carousel built-in widget and neither work with HTML according to the HTML tracker.

     

    If the widgets are not able to be seen, why include them in the in-built learning interactions at all? It just add a layer of frustration when I have already built the course around these two widgets. Any suggestions?

     

    Thank you

    Imogen

    RodWard
    Community Expert
    Community Expert
    December 14, 2019

    Something doesn't make sense here.  I just created a new blank CPTX with two slides and added both of those Learning Interactions from the button bar (Interactions > Learning Interactions) and they both worked fine in HTML5 and the HTML5 tracker did not list them as non-compliant.

     

    Did you perhaps insert your widgets by going to the Insert menu and choosing Widget, then selecting these from the list of widgets shown in the selection dialog?  If you DID that then you would have inserted SWF widgets, not HTML5 widgets.  That would explain why the HTML5 tracker picked them up, and why they did not appear when you published to HTML5.

     

    So, is that the likely issue? 

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    January 8, 2016

    You do not need to create a project as Responsive simply to have it play on tablets or mobile devices.

    If the widgets are known to be NOT HTML5 compatible, best not to use them at all.  IE11 will usually work with Captivate's HTML5 output, but your widgets are probably not going to work in this case.

    Inspiring
    January 8, 2016

    Thanks for your reply. Maybe I'm doing something wrong, then. The projects I uploaded created in a standard format (without scaling) would not launch in my tablet.

    jsvfoto9485530
    Inspiring
    January 8, 2016

    Rod is correct. Best not to use widgets that aren't HTML5 compatible if responsive development is your end game. Sounds to me like the widget you're trying to use is SWF. These won't work on tablets or other mobile devices. I have run into this before. I used the Jeopardy widget and it worked fine on the desktop, but failed on the iPad. Most desktop browsers still support flash, which is why the widgets will show up on something like Firefox. There's also this you can look at for IE11. If this is a short-term course there are workarounds, but if it's a long-term (as in you'll need access to it after browsers stop supporting flash) you may want to listen to Rod's advice.