Skip to main content
Participant
November 30, 2016
Question

Captivate 9 HTML5 Scalable HTML content freezing

  • November 30, 2016
  • 0 replies
  • 774 views

Dear Captivate team and fellow users,

I am well aware this has been called out as an issue in the past, but my question is when will Adobe address this?  I am in a shop where we are contractually obligated to deliver all of our training SCORMs via iPads, and given that, I would like to be able to use the "Scalable HTML content" option so that:

a) the content's resolution does not have to be so small (currently using 640x480 so that the content does not "chop off" when rotating between portrait / landscape)

b) the content is centered on the screen -- in Captivate 9, disabling Scalable HTML content results in the content being awkwardly top-justified on the screen, leaving undesirable whitespace (see part a).

Unfortunately, when enabling Scalable HTML content, the above issues are solved, but a new issue arises -- the course freezes on the first slide or never loads at all.  Total showstopper!

Because of this, I'm in a situation now where I may be forced to use Articulate Storyline 2 (something I loathe) simply because they are not experiencing the same issues with Scalable HTML content on mobile.   I inherited over 30 courses published in Articulate Storyline 2 which do not have the above issues when using Scalable HTML content.

I've heard theories passed around these boards about the root causes of this bug, but ultimately, there's a best practices page on these forums that simply advises developers to not use Scalable HTML content when publishing content for iPads.   That is an extremely disappointing answer, especially being in the situation that I am currently in with my clients.  While it was not my decision to develop for iPad only (and clearly not the decision I would have made), I have been advised this is not going to change here anytime soon.

My concern is that this feature was rolled out several years ago, and is still not stable.  It's my humble opinion that by now, this should have been fixed and we shouldn't be told to simply forego using a feature because it can't be / won't be resolved.

Any and all assistance would be hugely appreciated.   Thank you all.

    This topic has been closed for replies.