Side note on the nsIDOMGlobalPropertyInitialize method (from console API). It only works if I explicitly install an XPI. I can't get it to work in an add-on development environment (file in profile points to add-on), no matter how many things I remove/purge. I even tried creating a new profile and as the first thing, pointing to the dev env. No luck. But if I build and install the XPI, it works. Weird.
What does the category value actually end up as? Obviously the browser manifest registers an alternate category entry: http://mxr.mozilla.org/mozilla-central/source/browser/components/sidebar/src/nsSidebar.manifest#4 Assuming that the entry is correct, the code in here is "at fault": http://mxr.mozilla.org/mozilla-central/source/dom/base/nsScriptNameSpaceManager.cpp#725 It will not overwrite an existing entry (found during startup before extension are registered) with a new entry. I'm not sure why the code was written this way, but I'm pretty sure this is a DOM bug if it's a bug at all. volkmar made the change to do the correct dynamic category entries in bug 597809.
Component: XPCOM → DOM: Mozilla Extensions
QA Contact: xpcom → general
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
This is quite easy to do by defining functions on the wrappedJSObject, so i'm marking WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.