Closed Bug 500158 Opened 16 years ago Closed 8 years ago

Update the theme packaging document

Categories

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

Product:
Developer Documentation Graveyard
Component:
Add-ons
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: spitfire.kuden, Assigned: sheppy)

References

(
URL
)

Details

(Whiteboard: u=mozdev p=0 c=Add-ons)

The theme packaging that used chrome.manifest (contents.rdf isn't used) became possible four years ago. https://bugzilla.mozilla.org/show_bug.cgi?id=291946#c35 However, theme packaging document is written like this: > You must have a top-level chrome.manifest or contents.rdf file > which registers the chrome for the theme. https://developer.mozilla.org/en/Theme_Packaging Still, a lot of themes don't use chrome.manifest and contents.rdf is used. And, Bug 492008 was checked-in. contents.rdf has not worked any longer. It is necessary to update the theme packaging document for Firefox.next.
For starters, I've added a note explaining that contents.rdf is no longer supported. Someone needs to find time to substantially revise the theme packaging documentation.
A bit off-topic: Is there a way to inform theme authors which have written themes and will probably no notice this change?
And, Bug 371495 was checked-in. Theme cannot use aboutURL and optionsURL since Firefox 3.7.
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Whiteboard: u=mozdev p=0
Assignee: nobody → eshepherd
Component: General → Add-ons
Whiteboard: u=mozdev p=0 → u=mozdev p=0 c=Add-ons
I think this is no longer relevant.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.