Talk:Install Manifests
From MDC
- For addons hosted on addons.mozilla.org - Mozilla's update website may repackage your addon and correct or reject malformed version strings.
I believe this to be false. Can someone confirm it? --Nickolay 08:52, 27 October 2005 (PDT)
amo will definitely repackage the install.rdf and update the minversion/maxversion based on changes in the administration database. I'm not sure there *is* a malformed extension version string any more, so I can't see how it would reject one.
--bsmedberg 08:55:58, 2005-10-27 (PDT)
- See bug 313071. There Alan said UMO will not repackage the xpi, even at developer's request. Could you clear that one up, please? --Nickolay 09:03, 27 October 2005 (PDT)
I have not found a way to use the install manifest and keep some very useful version checking functionality based on InstallTrigger.getVersion code. The manifest doesn't offer the possibility of adding data to the Client Version Registry, or to perform installations without requiring browser restarts with refreshPlugins API.
The updateURL node is nice, but there is no way to force a check when the page loads for instance?
Other users have raised the same concerns: triggering automatic scripts (mozilla.devel.plugins)
--TTimo 2007-07-23
- Note that there's a plan to remove install.js support (bug 352762) and your comments here probably won't be read by many people. You should post your concerns to the appropriate newsgroup and try pinging bsmedberg/robstrong directly. --Nickolay 17:46, 24 July 2007 (PDT)
[edit] Bad em:localized example?
The example <em:localized> declaration used the <Description> tag, which comes from RDF. AFAICT, it should use <em:description> instead. Am I wrong? (Wouldn't be the first time ...) CWC 08:11, 3 February 2008 (PST)