Closed Bug 1259260 Opened 9 years ago Closed 7 years ago

chrome.manifest is not registered until startup()

Categories

(Developer Documentation Graveyard :: Add-ons, defect, P5)

Product:
Developer Documentation Graveyard
Component:
Add-ons
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: terrell.kelley, Unassigned)

References

(
URL
)

Details

:: Developer Documentation Request Request Type: New Documentation Gecko Version: unspecified Technical Contact: :: Details It's not a huge deal, but I spent a long time trying to figure out why I couldn't use an import to access a separate JavaScript file in a bootstrapped extension. It turns out that chrome registration is does not occur until just before startup() is called. It cannot be used in the setup outside that function. I think this should be in the documentation. ORIGINAL (excerpt): In Firefox 10 and later the chrome.manifest file located in the root of the add-on's XPI (i.e. a sibling of the install.rdf) is loaded automatically. SUGGESTED EDIT: In Firefox 10 and later the chrome.manifest file located in the root of the add-on's XPI (i.e. a sibling of the install.rdf) is loaded automatically before startup() is called.
Legacy extensions docs are no longer maintained. See the banner at the top of the page https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.