If you are testing from file:// and specify an http:// url, then it gets
loaded in a separate securitydomain and can't be used as a module.
Snce it worked when deployed, it implies that the app and the module are on
the same domain, so you shouldn't need to specify the domain in the URL and
just use relative paths and then it should work from file:// as well,
assuming the SWF is in the local copy of the configuration.
It works when deployed because the .swf is on a a domain which allowed cross domain.
The application is on my localhost and the .swf is on another online domain, so I can't specify a local path for the .swf.
If it was a problem of security domain why the error concerned the fact that the .swf is not a loadable module and not about security ?
Thank for your previous answer.
If you are loading a SWF from another domain when deployed, then you may not
be able to test from file:// because of the security rules.
Thank you for the answer.
Is it possible to change the security rules to allowed this ?
No. I wuld just deploy to a local server and set up your run/debug configs
to use http.