Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Buscar en Ayuda

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
Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.
Archivado

Something changed about WebExtension API in Thunderbird 143 (inline images not showing with some addons)

Thunderbird Extensions
siempredyc replied
siempredyc
siempredyc

Hi!

I'm using an add-on (ReplyWithHeader) that modifies the header displayed when replying to or forwarding emails. I have this problem: since Thunderbird v143, inline images no longer appear — they now point to an imap://fetch URL, so the images aren’t displayed. Several add-ons with similar functionality have the same issue. If you disable them, everything works fine (inline images are displayed correctly).

Developers of these add-ons say they rely on the WebExtension API (and probably the setComposeDetails function), so they can’t fix this on their side. Is there any way to confirm whether the Thunderbird API has changed since v140 (where these add-ons worked perfectly)? Could it be that, even if the issue seems to come from the add-on, there’s actually a bug in Thunderbird’s API?

If this isn’t the right place to ask about this, could you please tell me where I should post it?

I really need to modify the default reply header in Thunderbird, so this functionality is quite important to me.

Thanks in advance for your help!

Hi! I'm using an add-on (ReplyWithHeader) that modifies the header displayed when replying to or forwarding emails. I have this problem: since Thunderbird v143, inline images no longer appear — they now point to an imap://fetch URL, so the images aren’t displayed. Several add-ons with similar functionality have the same issue. If you disable them, everything works fine (inline images are displayed correctly). Developers of these add-ons say they rely on the WebExtension API (and probably the setComposeDetails function), so they can’t fix this on their side. Is there any way to confirm whether the Thunderbird API has changed since v140 (where these add-ons worked perfectly)? Could it be that, even if the issue seems to come from the add-on, there’s actually a bug in Thunderbird’s API? If this isn’t the right place to ask about this, could you please tell me where I should post it? I really need to modify the default reply header in Thunderbird, so this functionality is quite important to me. Thanks in advance for your help!

Todas las respuestas (2)

GerardoPcp04
GerardoPcp04
  • Top 25 Contributor

Hola, La ultima versión de Thunderbird es 144.0.1, la versión anterior 144.0.0 tiene alguna corrección con imágenes. Si hay un cambio de API debería esta en las Release notes: https://www.thunderbird.net/en-US/thunderbird/releases/ Pero yo no he encontrado algún cambio en ese sentido.

También he visto un problema similar con un complemento (Signature Switch) y fue resuelto por el desarrollador esta semana.

Yo creo que si el desarrollador considera que es un problema del Thunderbird debería abrir un caso en el foro de los desarrolladores: https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird&component=Untriaged

Saludos

siempredyc
siempredyc Autor de la pregunta

Estoy de acuerdo en lo que dices, es mejor acudir a Bugzilla a ver si realmente ha habido algún cambio interno que deban adaptar (que yo creo que es lo que tiene que haber ocurrido, porque es un problema generalizado en todos los addons de este tipo). El error persiste también en la última versión (144.0.1) y, como el principal interesado en que se resuelva soy yo, porque necesito esta funcionalidad, estoy intentando ayudar a los desarrolladores del addon a que me ayuden ;) Abriré un ticket a ver si hay suerte.

Gracias por tu respuesta!