[Project_owners] how does the shellblock.xpi work for FireFox?

Robin Monks devlinks at gmail.com
Sat Jul 10 19:14:33 EDT 2004


I'll admit that it has better organization.  But, it should have an
Execute external script tag in it so more intense operations can be
performed.

-Robin


----- Original Message -----
From: doron <doron at nexgenmedia.net>
Date: Sat, 10 Jul 2004 14:12:32 -0200
Subject: Re: [Project_owners] how does the shellblock.xpi work for FireFox?
To: Mozdev Project Owners List <project_owners at mozdev.org>




  
  


Truth be told, XPInstall was never designed for extensions - its apis
where hacked to make it work (register chrome and all).



install.rdf for extensions makes sense, because its only used to
install 1 extension and thus allows to gather information for
uninstallation.





Robin Monks wrote:



  I will always use .js.  I will never give in...  It has so much more
power and function.  Who would want to go to (gasp!) rdf?

-Robin

On Sat, 10 Jul 2004 10:59:18 -0200, doron <doron at nexgenmedia.net> wrote:
  
  

    For extensions in FireFox, install.rdf is now used.  install.js will
still be read if no install.rdf is found.  You have to remember that
install.js (XPInstall) is more powerfull, as it can set prefs, do
filesystem manipulations, and so on.



Charles Melhorn wrote:

    
    

      The patch for the 'shell:' protocol handling vulnerability,
(see http://www.mozilla.org/security/shell.html )
shellblock.xpi, contains two files: bug250180.js, which
disables the preference related to this problem, and
install.js, which seemingly adds the first file to the
"defaults/pref" folder.

I thought, however, that for FireFox 0.9.x the "install.js"
file was ignored by the Extension Manager, per the
documentation found here:

http://www.bengoodger.com/software/mb/extensions/packaging/extensions.html


   "install.js scripts are no longer used for Firefox and
   Thunderbird extensions. If you provide an install.js script,
   it will not be read|.|"

Clearly, though, the install script was not ignored, as the
new preference file was placed in the appropriate folder
upon installation in FireFox. Has the install.js functionality
been retained after all? Can someone point me to updated
documentation or discussion of this?

Thanks,

Charles



_______________________________________________
Project_owners mailing list
Project_owners at mozdev.org
http://mozdev.org/mailman/listinfo/project_owners
      
    
    _______________________________________________
Project_owners mailing list
Project_owners at mozdev.org
http://mozdev.org/mailman/listinfo/project_owners

    
  
  _______________________________________________
Project_owners mailing list
Project_owners at mozdev.org
http://mozdev.org/mailman/listinfo/project_owners


More information about the Project_owners mailing list