canmove, Confirmed users
1,570
edits
Extension Manager:Install Locations: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
==Distribution defaults== | ==Distribution defaults== | ||
This is an additional location, however it is not really an install location. It allows distributions to ship add-ons that the user then has complete control over. When a new version of the application is started, any add-ons here that have not been installed previously will be copied to the profile directory where the user may update or uninstall the add-on as they wish. | This is an additional location inside the application directory, however it is not really an install location. It allows distributions to ship add-ons that the user then has complete control over. When a new version of the application is started, any add-ons here that have not been installed previously will be copied to the profile directory where the user may update or uninstall the add-on as they wish. | ||
=Replacing flags= | =Replacing flags= | ||
The flags are mostly replaced by the behaviours of the install locations. <code>locked</code> and <code>appManaged</code> simply apply to all add-ons in the application directory. The exception is <code>hidden</code> which no longer exists for regular add-ons. If system administrators need to install an add-on that the user cannot see then they can do so by including it as a regular distribution bundle. These will not show up in the extension manager. The only downside is that certain add-ons may not work there if they use certain APIs like the nsIInstallLocation APIs to find their files. | The flags are mostly replaced by the behaviours of the install locations. <code>locked</code> and <code>appManaged</code> simply apply to all add-ons in the application directory. The exception is <code>hidden</code> which no longer exists for regular add-ons. If system administrators need to install an add-on that the user cannot see then they can do so by including it as a regular distribution bundle. These will not show up in the extension manager. The only downside is that certain add-ons may not work there if they use certain APIs like the nsIInstallLocation APIs to find their files. | ||