Skip to main content
Stagprime2687219
Legend
March 16, 2020
Answered

Greensock and Cross-Origin

  • March 16, 2020
  • 5 replies
  • 679 views

This one is for all those Greensock experts out there.

I recently became aware of Greensock through others posting questions about it in the forums.

It looked pretty cool so I decided to start messing around with it.

 

I used Greensock to create an animation and uploaded it as an HTML5 Animation into Captivate 11.5.1.499

 

When I do a preview - it behaves as expected and pulling data from the iframe works as well.

When I publish, however, the animation itself works fine but the data is no longer accessible. The file (the HTML embedded iframe one) becomes "restricted" and labeled as a cross-origin document.

 

The file, of course is dropped into the  /wor/wo_xxxx  folder and seems like it should be part of the same domain so I am struggling to find my way around this puzzle.

 

The console returns an ERR_FILE_NOT_FOUND about an "undefined" directory.

I am simply not finding the source/solution of this issue. Not sure why it is trying to find a directory by the name of 'undefined' in the first place.

Any ideas appreciated.

    This topic has been closed for replies.
    Correct answer TLCMediaDesign

    If you are previewing in Chrome or anything but IE11 this will happen, you need to upload to a server.

    5 replies

    TLCMediaDesign
    TLCMediaDesignCorrect answer
    Inspiring
    March 17, 2020

    If you are previewing in Chrome or anything but IE11 this will happen, you need to upload to a server.

    Stagprime2687219
    Legend
    March 17, 2020

    I've tried putting it out on a file server so that it wasn't local and that did not help.

    I will try a web server and see if that makes a difference.

    I did not encounter this issue with other HTML5 Animations where I pull data from the iframe.

    I figured it was due to the use of the extra JS files in this one vs pure HTML and CSS in the others.

    TLCMediaDesign
    Inspiring
    March 17, 2020

    If I use a link to a CDN JS library or webfonts, chrome throws a fit locally. Makes it very difficult to test in a browser depending on how I'm building a website. It won't run vtt files locally either o I either need to test in IE11 oe push them to the LMS to test. It's a pain when we are now required to develop with Chrome.