Not really, no.
-Boris
> Not really, no.
I find my solution -> in my security.js i've added this line:
##############################################################
......
user_pref("signed.applets.codebase_principal_support", false);
user_pref("capability.principal.codebase.p0.denied", "UniversalXPConnect");
user_pref("capability.principal.codebase.p0.id", "file:///");
user_pref("capability.principal.codebase.p1.granted", "UniversalXPConnect");
user_pref("capability.principal.codebase.p1.id", "search:///");
......
#############################################################
In this way i work with xpcom component in search:/// protocol, but no
with file:///.
ERRATA CORRIGE:
user_pref("signed.applets.codebase_principal_support", true);
This is relying on implementation details of the file: protocol (which we
actually want to change).
> user_pref("capability.principal.codebase.p1.id", "search:///");
Same here.
This wouldn't work for http://, of course.
-Boris
Note that this means that arbitrary untrusted websites can request privileges.
If what you really want is just to grant "UniversalXPConnect" to search:///, why
not leave that pref false? If that means the search:/// prefs don't work
(though they should), you could try
user_pref("capability.principal.codebaseTrusted.p1.granted", "UniversalXPConnect");
user_pref("capability.principal.codebaseTrusted.p1.id", "search:///");
-Boris