TB78 dropped support for the legacy API but Legacy WebExtensions using that can still be installed, if they do not have a strict_max_version set. :Sancus fixed ATN to automatically adjust the strict_max_version for these, so they connot get installed from inside the Add-On Manager However, the app fails to disable already installed Legacy WebExtensions on upgrade from TB68 to TB78. They remain enabled. This causes confusion and already produced a lot of error reports as users think such add-ons "should" work but fail on their systems and send bug reports. Furthermore, these add-ons do not get automatically updated, if there is a new version. Attached bug mitigates both issues. Currently it only searches for updates, but does not install them. It indicates an available update and I think that is enough.
Bug 1661216 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
TB78 dropped support for the legacy API but Legacy WebExtensions using that can still be installed, if they do not have a strict_max_version set. :Sancus fixed ATN to automatically adjust the strict_max_version for these, so they cannot get installed from inside the Add-On Manager However, the app fails to disable already installed Legacy WebExtensions on upgrade from TB68 to TB78. They remain enabled. This causes confusion and already produced a lot of error reports as users think such add-ons "should" work but fail on their systems and send bug reports. Furthermore, these add-ons do not get automatically updated, if there is a new version. Attached bug mitigates both issues. Currently it only searches for updates, but does not install them. It indicates an available update and I think that is enough.