The only way to do this now is to register a content policy in the content process using a frame script. That's how the shim stuff works internally. There's some reference to this at [1].
I'm working on an API that should make this easier in bug 1157561. It's not finished yet though. -Bill [1] https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_chrome_scripts On Wed, May 20, 2015 at 7:10 PM, Francois Marier <franc...@mozilla.com> wrote: > On 21/05/15 07:01, David Rajchenbach-Teller wrote: > > So is there something that ABP developers can do at the moment to > > reimplement their code without CPOWs & co? And is it documented anywhere > > on MDN? > > There's nothing like that at the moment, but I'd be happy to work with a > blocklist add-on developer to try and make it work. > > Francois > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
