Created attachment 440494 [details] a buggy extension Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:18.104.22.168pre) Gecko/20100420 Namoroka/3.6.5pre 1. Install https://addons.mozilla.org/en-US/firefox/downloads/latest/12025/addon-12025-latest.xpi?src=search 2. Install bug.xpi attached 3. Restart browser. Exit 4. Restart browser with -jsconsole In the Error Console you will see (along with normal errors): Error: Components.classes['@johnjbarton/testcomponent;1'] is undefined Source File: chrome://bug/content/overlay.xul Line: 6 This is incorrect. 5. FF > Tools > Addons > Extensions > Jetpack > select disable 6. Restart. Then you will see in the Error Console: Error: First Bug is that this does not show up Source File: file:///C:/Users/johnjbarton/AppData/Roaming/Mozilla/Firefox/Profilesfirstname.lastname@example.org/components/testComponent.js Line: 2 Error: uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXPCComponents_Utils.import]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///C:/Users/johnjbarton/AppData/Roaming/Mozilla/Firefox/Profilesemail@example.com/components/testComponent.js :: <TOP_LEVEL> :: line 5" data: no] Failed to load XPCOM component: C:\Users\johnjbarton\AppData\Roaming\Mozilla\Firefox\Profiles\bug\extensions\firstname.lastname@example.org\components\testComponent.js Error: Components.classes['@johnjbarton/testcomponent;1'] is undefined Source File: chrome://bug/content/overlay.xul Line: 6 These are the correct outputs.
Using https://addons.mozilla.org/en-US/firefox/addon/151809 in place of jetpack prototype I verified that this bug also applies to jetpack SDK 0.3
The first time after extension installation (when the XPCOM autoregistration happens) you see 3 errors, on subsequent restarts you get only the last one about component failed to register. Try: 7. Exit. Restart browser with -jsconsole (like you did after installing jetpack in steps 3-4) This is not related to jetpack at all. We just don't try register components over and over, even if the first attempt failed.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.