Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Calendar Entry, Description Field - No HTML?

  • 2 réponses
  • 1 a ce problème
  • 9 vues
  • Dernière réponse par terry61

more options

When creating or opening a calendar entry involving a meeting invite, any links in the the description field are in plain text. Sometimes extremely long strings making it difficult to select and paste into a browser.

Be nice to just be able to click the link. Does Thunderbird calendar support HTML at all? I know I can set the option for HTML in an email msg body, but not it seems in Calendar or Event 'description' fields.

Or am I missing something?

Many thanks in advance,

Terry.

When creating or opening a calendar entry involving a meeting invite, any links in the the description field are in plain text. Sometimes extremely long strings making it difficult to select and paste into a browser. Be nice to just be able to click the link. Does Thunderbird calendar support HTML at all? I know I can set the option for HTML in an email msg body, but not it seems in Calendar or Event 'description' fields. Or am I missing something? Many thanks in advance, Terry.

Toutes les réponses (2)

more options

This is a long-standing bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=553132

https://bugzilla.mozilla.org/show_bug.cgi?id=1535018

If you're creating an event, URLs can be added as attachments, and they are clickable, but invitations from other calendar apps might not provide the same option.

more options

Ahh, sorry, I didn't know it had been flagged before.

I'd actually discovered the 'attachment' option, but if there is any text before the url it bombs, i.e. "You have been invited to a meeting at https://xyz etc." - Meaning some mildly irritating editing still required.

Still, it's a work around for now, and also good to know it's a bug that's in the 'pipeline' so to speak. Hopefully fixed in the near future.

Thank you for taking the time to respond so quickly and looking out the links, much appreciated.

Terry.