Skip to main content
TLCMediaDesign
Inspiring
January 28, 2016
Question

TIP: Common JS Interface/SWF Frameset

  • January 28, 2016
  • 1 reply
  • 564 views

I've been struggling for the last two days trying out figure out why a SWF-based SCORM course was breaking when published to Blackboard.

Initially thought it was due to Blackboard adding code to my files in the content area. Which did cause a minor problem.

Come to find out after much digging, the culprit was in the Standard.js file on line 128: var lEventHandlerWin = window.parent;

As soon as the file is run in an environment with an actual parent window present, the Common JS Interface breaks.

The fix was to eliminate the parent: var lEventHandlerWin = window;

Voila, I'm back in business and don't have to recode my widget or the external JavaScript.

Haven't seen too many posts/if any at all about the CJSI not working, but hopefully this will help someone else down the road.

This topic has been closed for replies.

1 reply

Inspiring
January 29, 2016

Thank you TLC...I appreciate you taking the time to post the information.

TLCMediaDesign
Inspiring
January 29, 2016

Not a problem.

I can't imagine that others haven't run into this issue. I originally thought that the CJSI just didn't work well for swf, but I also coded everything inside of a navigation widget. This time I thought I would move a bunch of the progress tracking and SCORM calls to JavaScript that was shared by all modules for ease of updating. That's when I noticed the issue.