August 29, 2019
Html vs Flash and Chrome
Comments
(3)
August 29, 2019
Html vs Flash and Chrome
Newbie 1 posts
Followers: 1 people
(3)

We are in the process of migrating to an all html format and are using Captivate to reload our modules into our LMS (Currently ADP) the zip file that gets uploaded into our repository includes all formats  including PDF and  also supports ipad users Firefox and IE just fine. I want to know why Chrome users have a problem. Before you give me the typical answer “because its blocking flash” I want to know why the html file does not automatically play when flash is blocked? instead of the nut drill of having to explain they need to unblock Flash on Chrome. What will happen in Sept I think 2020 when Chrome will no longer support flash will the html file automatically play or will it all our files fail chrome?

3 Comments
2019-09-04 13:13:55
2019-09-04 13:13:55

@Tammy would totally agree if there were not so many companies who are still using SWF output and impose very outdated browser versions style IE9 or before. That is the reason why the SWF output is still there in Captivate I presume.

Like
2019-09-04 12:23:19
2019-09-04 12:23:19

I wouldn’t even include the Flash publish option since it will soon retire. Just publish using the HTML option and then the index.html file will be the launching file instead of the multiscreen.html file. The ability to publish to both was needed for several years while HTML5 matured. It has now. I don’t really see a reason why you would want to use the Flash option any more. My guess is that in the next full release or two the option to publish to Flash will be gone.

As to the ‘why’, that multiscreen.html option will check for the presence of Flash on the user’s computer. If it is there, that Flash option will be launched. There isn’t really a way for that file to know if there is something blocking Flash at a level above Flash itself.

Like
2019-08-30 08:18:03
2019-08-30 08:18:03

Since 3 years I only use HTML5 output and Chrome is my default browser although I also test on other browsers. Just to inform you that the problem should be elsewhere.

Chrome doesn’t support AutoPlay anymore, could that be the issue? I don’t know which version of Captivate you are using exactly, but since the second version of CP2017 Autoplay is automatically disabled for HTML5 output.

Another sentence wich bothers me is ‘including pdf’? Do you mean that you also publish to SWF and to PDF which needs an embedded Flash Player in the Adobe Reader? Do you use the dual publishing to SWF and HTML5?

Like
Add Comment