

HTML 5 courses published from Adobe Captivate freezes on the latest versions of Google Chrome Browser – 36.0.1985.125. We have investigated the issue and our findings are listed below . BTW ,we are still continuing to investigate if there any potential issue which is unknown at the moment and will keep you folks posted.
So far, we have found the following issues:
- Issue 1: HTML 5 content freezes on launch in Chrome 36 with a JavaScript error.
Reason: The support for deprecated methods ,noteOn and noteOff in the Web Audio API has been removed in the latest chrome update. These methods were deprecated in the standard a year ago but modern browsers still support these methods and the support was present in chrome till version 35. With Chrome 36, the support for these methods has been removed which results in content freeze and JavaScript errors:
- Issue 2: Slide backgrounds with gradients may not appear correctly.
Reason: Captivate uses SVG support to draw slide backgrounds.The w3c draft for SVG: http://www.w3.org/TR/SVG/struct.html#SVGElementWidthAttribute states that if width and height of SVG element is unspecified, the value should be internally treated as 100%. So, the SVG should be drawn on the entire rectangle. Chrome version 36 requires width and height to be explicitly specified due to this change, slide backgrounds may not appear correctly.
The good news is we have the fix for the above two issues and the steps to patch captivate are below
- Download this file https://files.acrobat.com/a/preview/04868973-1b29-46f1-9047-2be1fb6ecb80 and unzip it. You’ll find an index.html file.
- Go to [INSTALLDIR]/HTML file location. For example:
- Windows: C:Program FilesAdobeAdobe Captivate 7HTML.
- Mac: /Applications/Adobe Captivate 7/HTML.
- Replace the index.html present in the above location with the downloaded file.
Launch Captivate and from now on HTML 5 content will playback without any issues in Chrome 36. The fix is applicable to both version 7 and 8.
HTML 5 courses published from Adobe Captivate freezes on the latest versions of Google Chrome Browser – 36.0.1985.125. We have investigated the issue and our findings are listed below . BTW ,we are still continuing to investigate if there any potential issue which is unknown at the moment and will keep you folks posted.
So far, we have found the following issues:
- Issue 1: HTML 5 content freezes on launch in Chrome 36 with a JavaScript error.
Reason: The support for deprecated methods ,noteOn and noteOff in the Web Audio API has been removed in the latest chrome update. These methods were deprecated in the standard a year ago but modern browsers still support these methods and the support was present in chrome till version 35. With Chrome 36, the support for these methods has been removed which results in content freeze and JavaScript errors:
- Issue 2: Slide backgrounds with gradients may not appear correctly.
Reason: Captivate uses SVG support to draw slide backgrounds.The w3c draft for SVG: http://www.w3.org/TR/SVG/struct.html#SVGElementWidthAttribute states that if width and height of SVG element is unspecified, the value should be internally treated as 100%. So, the SVG should be drawn on the entire rectangle. Chrome version 36 requires width and height to be explicitly specified due to this change, slide backgrounds may not appear correctly.
The good news is we have the fix for the above two issues and the steps to patch captivate are below
- Download this file https://files.acrobat.com/a/preview/04868973-1b29-46f1-9047-2be1fb6ecb80 and unzip it. You’ll find an index.html file.
- Go to [INSTALLDIR]/HTML file location. For example:
- Windows: C:Program FilesAdobeAdobe Captivate 7HTML.
- Mac: /Applications/Adobe Captivate 7/HTML.
- Replace the index.html present in the above location with the downloaded file.
Launch Captivate and from now on HTML 5 content will playback without any issues in Chrome 36. The fix is applicable to both version 7 and 8.
You must be logged in to post a comment.

- Most Recent
- Most Relevant
With Captivate 9 and uploaded to scorm cloud I too am having a major issue with Chrome but an embedded video on a slide with its own player is not starting. I get a loading sign then nothing. In Safari everything runs perfectly. In Firefox I get audio but a green screen on the video. Any suggestions?
Hi Dr. Pooja.
I’m having problems in Google Chrome browser, the interactions are not displayed in this browser when exported in HTML 5. I’ve tried replacing the index.html file, it caused an error in Captivate that solved only by reinstalling the software. My Captivate is updated with the latest version and use the 32bit version. Any solution to this problem?
I found a way to fix this manually by editing the CPM.js http://captivatedev.com/2014/07/20/html5-captivate-projects-freezing-google-crome-v-36/
We just ran into this issue with Chrome as our learners have recently had Google Chromebooks deployed to them. The link above does not seem to be working again, does anyone know if a minor version update to Captivate 8 has address this yet? I’m currently on CP 8.0.0.145. It’s usually a burden getting updates installed by our IT staff who has to manually push updates. Thanks.
Please update to Captivate 8.0.1 and that should resolve the issue. Here are the details: https://elearning.adobe.com/2014/10/a-free-update-to-adobe-captivate-8-is-now-available.html
Hi Christophe,
Can you explain the issue, we like to investigate this.
You can also share your project with steps to reproduce to my mail id: agnihotr@adobe.com
Regards
Shriyansh
Adobe Engineering Team
Are these playback issues found in OSX 10.7 as well? I am in the process determining viability of team upgrade of Captiviate. Have not yet performed any of my own tests.
The “hardware-accelerated video decode” setting is not available in Chrome 36 on my Mac. “Sorry, this experiment is not available on your platform.”
This goes beyond the eLearning field, since it prevents Vimeo movies from playing for example. I don’t know why the Google folks decided to enable this parameter by default but it is really frustrating for users who need to find the problem by themselves before actually solving it.