Previously it might have been possible to launch Captivate published modules without having a web server environment. (It was certainly possble in the Flash/SWF days before Flash was killed off.) But HTML5 is a very different animal, and like it or not, the only guaranteed way to make sure it works is to play the content from some kind of web server.
You do not need to publish as SCORM and launch from an LMS for the purposes of doing content reviews and approvals. But you DO at least need to be able to have access to some kind of web server space from which you can give reviewers and approvers a hyperlink to the index.html file that launches your HTML5 module.
As you said, once upon a time in the early days of HTML5, this extra complexity of using a web server was not always necessary. But since Captivate 2019 was launched almost 4 years ago now there have been a lot of changes to the way web browser security works. There have been many security updates over the past few years, and each time the security has become more strict. This is another reason why you are not able to achieve playback in the same way you might have done it years ago.
Bottom line here is that the problem is not Captivate. It's simply a side effect of the way HTML5 web content now works on today's generation of web browsers.
I am a contractor creating e-learning for corportate clients and I run up against the same issues as you are describing here. I regularly have to set up some kind of web server environment to give managers and approvers access to my content long before we get to the point of posting it to the LMS. You need to start talking to your IT department and find out how this can be achieved within the company firewall.
7
Replies
AdChoices