Skip to main content
S
Stumbling Sal
Participant
December 15, 2011
Answered

Embedded SWF files auto starting in IE but set to not auto play - Chrome, Firefox, Safari work ok

  • December 15, 2011
  • 1 reply
  • 2381 views

One of the web masters at my school has embedded several Captivate 5 swf files in a web page.  I had re-exported all of them to not auto start after we realized that the originals were set to auto play upon loading (someone else made the orginials...).  Caches have been cleared on IE9, but yet, when that page loads, all of the no auto-play swfs start playing.  On Chrome, Firefox and Safari, none of them start playing when the page is loaded.  Does anyone have a clue why IE9 might be doing this and how to fix it?

Thanks,

Sue

This topic has been closed for replies.
Correct answer RodWard

Would the .js files be at all different for them?  Currently, we took just one of the .js files and are referencing it for all of the .swf files.  I have all of the .htm files separately, but when I originally exported, I did it in one folder, so the .js file just wrote over itself each time. I can reexport through Captivate if needed.


The JS files are most likely the same.  But keeping everything separate is always a good idea when it comes to elearning course modules.

1 reply

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
December 16, 2011

Am I correct in assuming that when your web developer set these SWFs up on the same page that he did not use the default HTM page that Captivate creates?  Did he just embed them into the web page using standard Dreamweaver code for SWFs?

Do the same Captivate SWFs start automatically if you upload them to your web server individually with the HTM and JS files that Captivate creates?  If not, then your web developer might be better off embedding the content in his web page using individual iframes pointing at the HTM file rather than the method he previously chose.

S
Stumbling SalAuthor
Participant
December 19, 2011

Yes, you are correct.  They are taking 5 different Captivate outputted files and embedding them all on a different HTML page (technically, it's being done on Drupal, if that makes a difference). 

They haven't tried to upload them separately, so I'm not sure. 

Since it's only autostarting in IE, it just seems strange.

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
December 20, 2011

For some features in a Captivate SWF file to work properly it requires the HTM and the standard.js file that Captivate outputs at publish time.  You should ask your web developers to upload all three files (HTM/SWF/JS) to a folder on the web server and then try creating an inline frame (iframe) in these Drupal web pages to then call the HTM file in the frame.  If the project plays as desired in all browsers, THEN you know the previous issue was due to not launching the SWF in the way Adobe originally intended.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices