ChatZilla:Suiterunner
Jump to navigation
Jump to search
Aims
- Make ChatZilla work on (currently experimental) Toolkit-based builds of trunk SeaMonkey ("Suiterunner").
- Don't confuse SeaMonkey users that don't use ChatZilla.
- Allow SeaMonkey users to update ChatZilla...
- ...as part of new SeaMonkey releases.
- ...as an extension in the same way they can in Firefox.
- Retain makexpi.sh for standalone XPI building requiring only mozilla/config.
Building as an extension
- Need to ifdef MOZ_XUL_APP in the main Makefile.
- Add variables like
extensions/inspector/Makefile.in#51. - Need to preprocess install.rdf (and static.js).
- That, or update versions in multiple places whenever CZ or SM bumps.
- chatzilla-version.txt?
- No effect on makexpi.sh builds, if we do it right.
appManaged
- Used in install.rdf files.
- If it's on:
- It prevents the EM doing update checks and showing incompatibility warnings.
- Newer versions of ChatZilla can still be installed, they end up in the profile and override the app version.
- If it's off:
- The EM will check for updates only if the app directory is writable. However, any accepted updates will go to the profile anyway.
- The new add-on update notification may annoy users if they don't even use ChatZilla.
locked
- In install.rdf, prevents an add-on from being uninstalled. Do not want.
Updates
- If a user has installed a ChatZilla update as described above, any new versions installed to the app directory as part of SeaMonkey won't be active.
- Blocklisting will save us if we have a security issue. :)
Stuff the EM could support
- Disable updates on appManaged extensions by default, but offer to enable them in the EM UI.
- Allow updates for a specific extension to be disabled from the updates window, so a user can get rid of the annoyance without uninstalling us.
- Keep appdir extensions enabled in safe mode. ChatZilla would revert to the SeaMonkey bundled version, which seems safe.
- How do we (CZ) handle downgrading?