On 8/6/2012 12:00 PM, Matthew Gertner wrote:
I guess the "interfaces" directive is not support in the chrome.manifest of
bootstrapped extensions. We're using nsIComponentRegistrar.registerFactory to register
XPCOM components, but we also need to register some additional XPCOM interfaces.
I'm worried about the premise. Registering an interface is a
non-reversible process. This means that it is easy to cause weird bugs
where somebody tries to update your extension while running (which is
one of the good things about restartless addons!) but it doesn't work
right because both the old and new "fooIYourInterface" are loaded at the
same time.
I'm having trouble thinking of a reason any extension without binary
XPCOM components would need to register an interface.
It's technically possible to do this using
nsIComponentRegistrar.autoRegister and a manifest file, but I strongly
recommend doing something else (catch me on IRC to talk if you want).
--BDS
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
