Closed Bug 51209 Opened 26 years ago Closed 25 years ago

XPI should check for an appropriate version of mozilla

Categories

(SeaMonkey :: Installer, enhancement, P3)

enhancement

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: mozilla, Assigned: ssu0262)

References

Details

Currently when you try to install an xpi package from themes.org, for example, sometimes the install will fail because it is not compatible with the user's version of mozilla. The XPI should know the version of mozilla that it was made for and warn the user if it doesn't match.
That's a must for a good install routine IMO, but it's tricky. It shouldn't warn, tha the user uses a Mozilla build and the package is for the corresponding Netscape build (or vice versa), to ensure free exchange of packages. However, the versions might differ slightly, e.g. a Mozilla skin might not have icons for AIM.
Warnings should differ depending on relative versions. Older browser w/ newer package spec should be a serious warning browser slightly newer than package spec should have an optional caution browser much newer than package spec should explain that it's newer and that the package might not work.
I fail to see what specifically the xpinstall team should do for this bug. Currently it is difficult-to-impossible for a script to know which version of Mozilla it is running on (bug 7022), but once that's fixed it's really up to the script author of each individual package to determine which versions of Mozilla it's compatible with and issue appropriate warnings. Some things (e.g. add-on packages like chatzilla) might be compatible with a wide range of versions, while others might work for only a few days worth of builds (e.g. language packs where missing DTD entities cause entire pages not to render). If there are particular packages misbehaving please write bugs on those packages, or if I've misunderstood the thrust of this bug feel free to clarify and reopen. Also keep in mind that since the download itself can tend to be the expensive part, it's often worthwhile to do as much checking as possible on the serving end.
Status: NEW → RESOLVED
Closed: 25 years ago
Depends on: 7022
Resolution: --- → INVALID
You have a point.
vfy
Status: RESOLVED → VERIFIED
*** Bug 211209 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Component: Installer: XPI Packages → Installer
QA Contact: agracebush → general
You need to log in before you can comment on or make changes to this bug.