There are many scenarios that lead to an empty Disconnect panel (when clicking its toolbar button):
Remove it from the toolbar, restart Firefox, enter customize mode, place it anywhere. If you click it now it won't work.
Place it in any Puzzle Toolbar and restart Firefox. Because those toolbars (as well as any other created through CustomizableUI.jsm from other add-ons) are created asynchronously, its items can't be placed there when Disconnect initializes (synchronously) with Firefox.
I was going to create a simple pull request that calls Disconnect.initialize() through a simple CustomizableUI listener every time the Disconnect item is placed in a toolbar node, so that it's sure to exist then and the initialization process can finish. But by then it has surely run at least once, and there is just so much going on in that initialize method that I don't know if it can be called multiple times or not (I'm guessing not because things get weird if I call it multiple times through the console).
So there needs to be a flag somewhere that controls whether the button/panel have been initialized yet for this to work properly.
There are many scenarios that lead to an empty Disconnect panel (when clicking its toolbar button):
I was going to create a simple pull request that calls
Disconnect.initialize()through a simple CustomizableUI listener every time the Disconnect item is placed in a toolbar node, so that it's sure to exist then and the initialization process can finish. But by then it has surely run at least once, and there is just so much going on in thatinitializemethod that I don't know if it can be called multiple times or not (I'm guessing not because things get weird if I call it multiple times through the console).So there needs to be a flag somewhere that controls whether the button/panel have been initialized yet for this to work properly.