Copy link to clipboard
Copied
Learning interactions function differently in F10 preview than when published (HTML5). There are components (text box for instructions & "Next" button) that do not come through into the published product. When viewed in Chrome, we see the learning interaction minus the programmed audio, instructional text box, & "Next" button. When viewed using IE, the learning interaction does not appear but the instructional text box & "Next" button do appear. (We do not have an LMS, but post onto our own server.) Any insight?
Copy link to clipboard
Copied
For HTML output in a non-responsive project, you have to use F11 (Preview HTML in Browser)/ All other preview methods (except SCORM Cloud) use a temporary SWF file. Is this a non-responsive or a responsive project? If it is responsive, which workfow: Fluid Boxes or Breakpoints?
As for Chrome: at this mometn AutoPlay is forbidden on Chrome, That is probably the reason why you don't hear audio.
Copy link to clipboard
Copied
It is a non-responsive project. Just wish we could figure out why the interactions act differently than how programmed in Chrome & IE. Our courses are available to approximately 100,000 people, so we really need them to work the same in multiple browsers.
Copy link to clipboard
Copied
It is sort of wishful thinking, because browsers do not all support HTML5 the same way, and make decisions like Chrome to turn off AutoPlay.
You could turn off AutoPlay in Captivate, and insert a poster image and eventually a custom play button like I explained in: https://elearning.adobe.com/2018/03/get-rid-white-start-screen-black-button-html-output/
At least that will ge you rid of the difference between Chrome and other browsers.