Hi,

> If trustContent=false, the SWFLoader doesn’t know it loaded another Flex
> SWF.  There is code in SWFLoader that tries to size loaded Flex SWFs
> differently than other SWFs.

From what I can see (but not 100% sure) it's loadForCompatibility not 
trustContent. Setting loadForCompatibility to true breaks the sizing of all 
examples not just the 3rd party ones.

> We have to decide how secure we want to be.  If we accidentally leave a
> hole where someone can inject a URL to load, it might get exploited.  If
> we put a whitelist in an XML file on our server, that might be secure
> enough.

AFAIK Having trustContent = false is the most secure, which is what we 
currently do.

Thanks,
Justin

Reply via email to