I've published a ton of eLearning lesson using Adobe Captivate, and I have seen the Publish dialog box more times than I can count. Sometimes I get tunnel vision when working in a tool I've used for so long and often fail to notice when tiny little options are added to a dialog box.
Take the Scalable HTML content check box for instance. If you hadn't noticed the option in the lower right of the Captivate 6 Publish dialog box, join the crowd.
The Scalable HTML content option is off by default, leading me to believe is wasn't necessarily a good idea to use it. I was curious what the option would do, so I enabled it and published a SWF. When the lesson opened in my web browser, the value of the option became clear. If you record a lesson at 800x600, and the learner's display is large, the 800x600 will float horizontally in the browser window. If the learner maximizes the web browser, the 800x600 lesson keeps its original size, and continues to float (the learner will see more white space to the left and right of the lesson).
However, with Scalable HTML content enabled in my test project, the published SWF always resized to fit my browser window (proportionally), no matter how big or small I made my browser window. I was concerned that the quality of the SWF would suffer if I made my browser window too big (I have a pretty large display). I was pleasantly surprised when the lesson continued to look pretty good, even when I maximized my browser window.
The only downside to using Scalable HTML content that I'm aware of (I asked Adobe to confirm this), is that performance will suffer if the lesson is opened on an Apple iPad. (Yes, Scalable HTML content works if you publish as a SWF or HTML5. Of course, given Adobe's warning, I'd be hesitant to use the option with HTML5 output.) If you've had issues with Scalable HTML content, please share.
Looking to learn Captivate quickly? I teach two live, online Captivate 6 classes. Adobe Captivate Essentials and Adobe Captivate Beyond the Essentials (Advanced).
the scalable html content for html5 does not work inside of a frame/iframe.
it also ignores zoom level.
this means if it is in a frame, it will always go off of the applications dimensions (e.g. chrome/firefox/ie), not the frames dimensions. this causes clipping of the content inside the frame.
Posted by: billyd | July 02, 2013 at 06:13 PM