Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

add-on support

  • 1 antwoord
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur christ1

more options

Maybe my question is not appropriate for the support forum.

On the site: https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 I've read the following sentences: "Thunderbird 57-60 and beyond and Seamonkey will still support these as legacy add-ons if the appropriate modifications are done to the add-on to adapt to the changed interfaces. " "Thunderbird will be adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons. "

Does this mean if a developper adapt his legacy add-on in the future to the changes of legacy interfaces (not webextension api's), his add-on wil stil work in the future versions of thunderbird?

Maybe my question is not appropriate for the support forum. On the site: https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 I've read the following sentences: "Thunderbird 57-60 and beyond and Seamonkey will still support these as legacy add-ons if the appropriate modifications are done to the add-on to adapt to the changed interfaces. " "Thunderbird will be adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons. " Does this mean if a developper adapt his legacy add-on in the future to the changes of legacy interfaces (not webextension api's), his add-on wil stil work in the future versions of thunderbird?

All Replies (1)

more options

It depends on the actual add-on. Thunderbird is adopting the changes Firefox does. If interfaces used by legacy add-ons are being removed in Firefox, this will ultimately affect Thunderbird legacy add-ons as well. So the only possibility for an add-on author may be to create a hybrid extension (aka embedded WebExtension). Not every extension author may be willing to do this. You might as well ask your crystal ball about what will happen beyond TB60.