Well, I have tried the option 1 (set the following flags for the custom
protocol:
URI_NORELATIVE | URI_NOAUTH | URI_IS_UI_RESOURCE).
All worked fine until I have tried to have a build based on Mozilla-1.9.1.
Then either the scripts which are sent via this protocol are not run at all,
or if I add the setting
user_pref("signed.applets.codebase_principal_support", true);
then the scripts run but with the warning every time the page is loaded. Is
there something else I could do? I have to get the scripts sent via this
custom protocol from the remote server, there is no easy way around this.
Boris Zbarsky wrote:
>
> Anna Nachesa wrote:
>> Anyway, I guess I either have to change the content so that it doesn't
>> lilnks to chrome or to tweak SecurityManager so that it doesn't restrict
>> our
>> protocol. I would prefer the first option.
>
> Yes, the first option is the way to go.
>
> -Boris
>
--
View this message in context:
http://www.nabble.com/nsScriptSecurityManager-and-a-custom-protocol-tp22227469p22621767.html
Sent from the Mozilla - Embedding mailing list archive at Nabble.com.
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
