Closed Bug 527843 Opened 15 years ago Closed 14 years ago

Make sure all extensions marked as 3.6 compatible have chrome.manifest files

Categories

(addons.mozilla.org Graveyard :: Administration, defect, P5)

Product:
addons.mozilla.org Graveyard
Component:
Administration
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: jruderman, Unassigned)

References

Details

Extensions without chrome.manifest (but with contents.rdf) can't be *installed* in Firefox 3.6, but if already installed, will continue to work.  This confused me enough that I marked my extensions as compatible with Firefox 3.6 even though they couldn't be installed in Firefox 3.6.

I'm worried that other extensions might be marked as compatible with Firefox 3.6 even though they can't be installed there.  I think new uploads get checked, but version-bumping doesn't.  So I guess I want this check to be run against extensions that are currently marked as compatible with 3.6, and whenever an extension's maxVersion gets bumped (to be compatible with 3.6).
Severity: normal → trivial
Depends on: amo-mxr
Priority: -- → P5
Target Milestone: --- → Future
Firefox 3.6 has been out long enough now that I think these issues have sorted themselves out.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.