582164 - Build chrome urls into bootstrap for Firefox 4

Status: RESOLVED DUPLICATE of bug 564667

(Add-on SDK Graveyard :: General, defect)

Description

[James Hartig]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.477.0 Safari/534.3
Build Identifier: 

https://bugzilla.mozilla.org/show_bug.cgi?id=581862 says that in Firefox 4, you can no longer use chrome.manifest files to register chrome urls. This makes it impossible to register a optionsURL and otherwise have a preferences window. For my app, this is required. Are there any known workarounds? In Firefox 3.x chrome.manifest files are still read so we are ok, until they switch.

Reproducible: Always



Expected Results:  
Some method of registering chrome urls in Firefox 4.x

Comment 1

[James Hartig]

Could also be alleviated by: https://bugzilla.mozilla.org/show_bug.cgi?id=564667

Comment 2

[Myk Melez [:myk] [@mykmelez]]

The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".

Comment 3

[Dave Townsend [:mossop]]

Is this bug just a duplicate of bug 564667 or is there something else I'm missing?

Comment 4

[Myk Melez [:myk] [@mykmelez]]

This is something we should address when we start working on our XUL addon migration strategy and tooling.

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Actually, when I take a second look at this bug, it is indeed a duplicate of bug 564667 (although we'll be addressing the issue of a settings dialog for SDK-based addons without requiring chrome registration via separate work).