title: SWF sandbox violation Error #2060 in Chrome
body: <p>I am embedding a SWF object from a CDN into a page using <a href="https://code.google.com/p/swfobject/wiki/documentation" rel="nofollow noreferrer">swfobject</a>.</p>
  
  <pre><code>var flashvars = {};
  var params = { allowscriptaccess: "always"};
  window.swfobject.embedSWF(self.options.img_url+'/click2call.swf', "ISC2C_SwfContainer", "1", "1", "9.0.0", flashvars, params);
  </code></pre>
  
  <p>However, when I load the page in Chrome, I get this error:</p>
  
  <blockquote>
    <p>SecurityError: Error #2060: Security sandbox violation:
    ExternalInterface caller <a href="http://cdn.url/SWFObject.swf" rel="nofollow noreferrer">http://cdn.url/SWFObject.swf</a> cannot access
    <a href="https://na1.salesforce.com/00Q/o" rel="nofollow noreferrer">https://na1.salesforce.com/00Q/o</a>.     at
    flash.external::ExternalInterface$/_evalJS()  at
    flash.external::ExternalInterface$/call()     at SWFObject/initApp()  at
    SWFObject/___swfobject_Application1_applicationComplete()     at
    flash.events::EventDispatcher/dispatchEventFunction()     at
    flash.events::EventDispatcher/dispatchEvent()... error continues for a
    while.</p>
  </blockquote>
  
  <p>I read that this error can be solved by the AllowScriptAccess flag so I added that. </p>
  
  <p>I also read in <a href="https://stackoverflow.com/questions/1817339/google-chrome-extension-in-flex">this SO answer</a> it seems to be a bug with Chrome that the Chrome Flash plugin cannot be sandboxed? - <a href="https://stackoverflow.com/questions/1817339/google-chrome-extension-in-flex">sandbox bug answer</a></p>
  
  <p>This seems to be true as I was able to embed, load and use the object successfully in Firefox. </p>
  
  <p>I have the Security.allowDomain("*") set as mentioned by <a href="https://stackoverflow.com/questions/4698506/actionscripts-externalinterface-addcallback-only-working-locally-not-in-produc">this answer</a>. I don't have the Security.allowInsecureDomain set. </p>
  
  <p>Is there a way to fix this error in Chrome? </p>