Closed Bug 330212 Opened 19 years ago Closed 19 years ago

EM can't handle extracted old style format Theme in extensions dir

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: mossop, Unassigned)

Details

Maybe this is a wontfix, but if you extract an extensiion into a directory in the extensions dir and call it by the extension ID then start firefox, it detects and installs the extension. If you do the same for a theme (I think only old-format themes) then it throws an chrome registration error. Inidentally, whne does the EM get it's own component in Toolkit?
Sorry, I meant old-format theme as in a theme that used contents.rdf rather than chrome.manifest.
I noticed an error while debugging yesterday that may be related though I'm not sure if I added support for extracted theme dirs when I fixed theme installs way back when but I thought I had. If this works on branch and not trunk then it may be due to a recent patch I landed. I'm not sure if the EM will be moved to toolkit since some people using Firefox would have trouble finding it then... personally I think it would be a good thing to do and I've been meaning to bring it up to a couple people.
Finally took a quick look and I didn't add support for old style themes. The reason I added the new format for themes was specifically to bring this and other capabilities (e.g. chrome.manifest, flat file packaging, etc.) that are available with extensions to themes. Since we support this with the new format and that the additional checks that would need to be performed to support this with the old style format are rather prohibitive (e.g. we require the install.rdf to be in the theme directory's root and others) I'm going to wontfix this.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Summary: EM can't handle extracted Theme in extensions dir → EM can't handle extracted old style format Theme in extensions dir
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.