Potential Functionality Issues (Security) with HTML Content

Question

Good day, all;

I am having an issue with HTML content from Captivate and I'm not sure there's anything I can do about it or, if there is, what that might be.

I created a Captivate lesson for my institution last year that was fairly straightforward. It had graphics, audio and a few questions which I built (rather than use the question feature). The lesson was exported as a SCORM package and no issues were encountered by any of the nearly 100 people who completed it.

For this year, however, the institution requested me to publish it as an HTML package as they wanted to offer it on the website (rather than within the LMS). I packaged it and sent it off as requested and while it functionally works, it got rejected by IT due to some issues as quoted below (from two separate emails to me)(red text added by me):

The first, when I said there was nothing in the file (meaning I had added no links to external widgets, etc.): "However, the files you provided...also include outdated versions of JavaScript."

The second, when issues were checked from the IT side: "These materials, which were originally created in a local environment, relies on proprietary JavaScript files (e.g., cp.js, cpXHRLoader.js) that must be properly loaded for key features—like interactive elements, slide transitions, and media playback—to work correctly. If these files are missing, misconfigured, or not properly referenced, functionality may break when moved to the live site."

Based on these points the lesson has been rejected "until an updated version that resolves these issues" can be provided. Unfortunately, I don't know how to fix this or if it can be fixed. I just published normally as an HTML file in Captivate without doing anything special.

I created this lesson on a Mac, using Adobe Captivate 2019 (11.5.5) (which my 'check for updates' look returns as being up to date).

Has anyone come across anything like this before? Or are there any ideas of how I can fix the identified issues? I don't want to have to build this whole thing again in another program, so any suggestions of how I can rectify this would be appreciated!

Thanks!

RodWard · Answer

I would certainly suggest that you DO update your Captivate 2019 version to the latest available (11.8.x).

But that isn't necessarily going to automatically fix what your IT department are complaining about.

I am assuming by their statement about "outdated versions of Javascript" they are probably referring to the fact that Captivate 2019 still uses some JavaScript functions that modern browsers no longer support. However, that doesn't mean that anything bad is going to happen as a result. I would be asking your IT department to specify exactly WHICH JavaScript issues they object to. Their statement is vague.

As regards their other complaint about "proprietary Javascript files" this too is somewhat ridiculous. The cpm.js file is a huge Javascript file that is constructed directly from your Captivate CPTX project file and of course it must be properly loaded for everything to work properly. The cpXHRLoader.js file is also custom generated at publish time. But if your IT department had actually opened that JS file they would have seen that permission is given for the file to be used in output. So in what way are these files unable to be used?

A typical Captivate HTML5 output ensures that all required files are encapsulated inside the output folder. When you test Preview the project on your development computer (yes it could be called a 'local environment') you are basically just running the output inside a temporary localhost webserver that Captivate creates for the occasion. If the content can run in your localhost webserver then it should also work on your organisation's web server as well. Did the IT department actually TRY to copy the output to a folder on their TEST webserver to see if it worked? It does not appear that they have done so.

Honestly, I think your IT department are just being difficult to deal with.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded