I am using Captivate 2017 (10.0.1.285) and publishing as scalable HTML5. It runs perfect everytime in IE. However I get random problems when run in Google Chrome and Edge. The problems always involve smartobjects. Sometimes they won’t display or will display the background but not the text (The text has a variable). It is very frustrating because it does not happen all the time. Has anyone else had issues with smartobjects in Chrome and/or Edge?
Did you run the HTML5 Tracker under the project menu? I’ve had some troubles like this in the past, and there was no indication that features are unsupported in HTML5, but they show as “unsupported” in the HTML5 Tracker window. I’ve dealt with them by removing unsupported options/features from the project.
I think they should remove the option to publish in Flash and all the Flash only elements from Adobe Captivate. At this point anyone who is still using Flash, probably won’t be upgrading their Adobe Captivate anyway. Am I wrong? Is anybody still publishing to Flash?
mark –
Sorry to disagree. Lot of companies still do use SWF output, and old browsers. Maybe weird to you but that is just the case.
I guess my point was, that in those situations people probably aren’t updating to the latest version of Captivate every year.
It’s also worth mentioning that Adobe will discontinue all support of Flash by the end of next year and as a matter of policy has announced they “encourage content creators to migrate any existing Flash content to these new open formats.”
mark –
Perfectly know that Adobe stops support for the Flash Player (which is not the same as the Flash application, now named Animate CC). Old browsers still have the Flash player plugin built in. I have done my part of telling developers to switch to HTML output, but be sure that not everyone is listening. Companies can be very stubborn in postponing.
I have narrowed down what is going on, (trying to find a work around now that is not too much rework). The problem is sometimes smart objects in Chrome and Edge don’t display. However after some researching I realized they are displayed but they are just not being drawn to the screen in the proper order so they might be drawn underneath something else. However when you actually rollover the area or resize the browser window, the browser refreshes the screen and fixes the issue. This issue never happens in Internet Explorer but happens inconsistently in Chrome and Edge. Sorry to say, since I have no control over the Browsers or Captivate, I have to find a work around within the constraints of this bug.
Second link (published with CP2019):
First link, was pointing to a project published with CP2017. This one to compare to see if there is a difference.
First
The issue happens running from a webserver. I have tracked down that it happens with scalable html5 is selected. And sometimes the items show up if you resize the browser. So, I would guess the issue is something to do with how different browsers render. This is a major issue for this project.
Have no longer access to CP2017, which is a pity. I always publish blank projects to scalable HTML5 output and shapes are my favorite objects, can’t remember having seen that problem. Of course meanwhile browsers will have gotten updates. I will post a couple of links to that type of output which I published with CP2017. Can you check if you see the same problem? Will do in a separate comment, not sure if they’ll get some moderation delay.
BTW my default browser is Chrome and I use Edge as alternative sometimes (as I do Firefox).
How do you test? HTML5 output is meant to run after uploading to a webserver or a LMS (if it is a SCO).
You must be logged in to post a comment.
