On 4/29/06, Michael Vincent van Rantwijk <[EMAIL PROTECTED]> wrote:
Christian Biesinger wrote:
> HJ wrote:
>> Seems like a registered component, so why doesn't it work?
>> Has something been changed recently that I should know?
>> Is there some invalid code in it?
>
> This probably doesn't explain your problem, but getClassObject should
> accept nsISupports as well as nsIFactory, and mzContentNotifier probably
> needs neither nsIObserver nor nsIFactory.

Christian,

My father is gone for the next 5/6 months again so I'm stuck with this
problem now, and I desperately need help so can you please get this
component working in a trunk build?

The component itself is working fine, it's that your component is not
registered as a content policy handler. To do that, you should pass
your component's contract ID as a value of the category entry you're
adding, i.e.:
-    this.getCategoryManager().addCategoryEntry("content-policy",
this.mContractID, "", true, true);
+    this.getCategoryManager().addCategoryEntry("content-policy",
this.mContractID, this.mContractID, true, true);

This is what all code in the tree implementing content policies does, anyway.

As far as I can see, the change that broke you was the patch in bug
246092. You may want to complain there as well as fixing your code.

Nickolay
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom

Reply via email to