The new flat chrome manifests are currently not usable by extensions because the manifest is overwritten while doing compatibility. This patch makes sure that we upgrade/delete/manage the chrome.manifest files in an extension properly such that extensions can include a chrome.manifest in the root of their XPI.
Created attachment 175345 [details] [diff] [review] Delete/extract/overwrite chrome.manifest correctly
Attachment #175345 - Flags: first-review?(shaver)
Comment on attachment 175345 [details] [diff] [review] Delete/extract/overwrite chrome.manifest correctly I would like a more descriptive comment than "doing the RDF thing", perhaps "generating one from contents.rdf data", but with that I am pleased to r=shaver.
Attachment #175345 - Flags: first-review?(shaver) → first-review+
Fixed on trunk. Updated documentation is at http://www.mozilla.org/projects/firefox/extensions/packaging/extensions.html I could use help spreading the word about this checkin amongst extension authors. My blog is down from having moved websites and not configured the new one yet.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8beta2
I'll make a thread on MozillaZine and get a mod to sticky it. How's that?
http://forums.mozillazine.org/viewtopic.php?t=228092 is the thread I created.
> I could use help spreading the word about this checkin amongst extension > authors. My blog is down from having moved websites and not configured the new > one yet. You can have a front page MozillaZine article if you like. Just write something and send it via http://www.mozillazine.org/submit/ and I'll put it up.
Component: XRE Startup → Startup and Profile System
QA Contact: nobody → startup
You need to log in before you can comment on or make changes to this bug.