Confirm
587
edits
Changes
no edit summary
2. If the add-on is not marked as compatible, Firefox will look at its install.rdf to see if the author has opted out of compatible by default and requested strict compatibility mode. If they have, the add-on is incompatible and should be disabled in the new version of Firefox.
3. Next, Firefox will look for binary components in at the add-oncompatibility info, to see if the specified minVersion is greater than the running appl;icatin's version. If binary components are foundit is, then Firefox will assume the add-on addon is not backwards compatible, and mark it as incompatible and should be disabled in the new version of Firefox.
4. Next, Firefox will look for binary components in the add-on. If binary components are found, the add-on is incompatible and should be disabled in the new version of Firefox. 5. Finally, for all add-ons, Firefox will look at the metadata it received from AMO and the compatibility presented there will override all of the previous checks. AMO may report that the add-on is actually not compatible with the new version, or it may report that it is compatible with the new version. If there is no compatibility information returned for the particular version of the add-on with the particular version of Firefox, the compatibility is unchanged from steps 1-3.
Firefox will then inform the user, if necessary, about incompatible add-ons, or update to the new version and automatically enable the add-ons that would otherwise be incompatible.
