On Thursday, June 5, 2014 5:50:23 PM UTC+2, Boris Zbarsky wrote: > The CSP implementation should be using protocol flags here instead of > hardcoding (and if it's not, bugs should be filed). And then your > protocol can set the relevant flags.
Bug filed: https://bugzilla.mozilla.org/show_bug.cgi?id=1021669 I got around this for the time being by registering my own @mozilla.org/cspservice;1 that delegates to the original one. Don't try this at home, kids. If you do try this at home, remember to refresh the category cache for content-policy if you want the change to be taken into account when you install a bootstrapped extension: var subject = Cc['@mozilla.org/supports-cstring;1'].createInstance(Ci.nsISupportsCString); subject.data = 'CSPService'; Services.obs.notifyObservers(subject, 'xpcom-category-entry-removed', 'content-policy'); Services.obs.notifyObservers(subject, 'xpcom-category-entry-added', 'content-policy'); And, of course, remember to put back the old factory when your extension is uninstalled (and refresh the category cache again). _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
