TB 91 does not show calendar invite details, only accept/tentative/decline
SInce a recent upgrade (o currently 91.2.1 (64-bit)) my TV for Mac is no longer showing calendar details
TB apparently recognizes the relevant MIME part as it shows the 'This Message contains an event [Accept]/[Tentative]/[Decline]...." banner
see attached pic
However there is no indication of the calendaring details shown
Note: I am not using Lightning myself. I need to accept the event in another calendaring app, but it would be very useful to at least be shown the details when I browse my emails
In Outlook (for Mac) these show just fine
The calendar invite is included in the email in a MIME part (last part in the message) which decodes as
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="*****":MAILTO:***** ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Koerber, M
athias":MAILTO:mkoerber@akamai.com
DESCRIPTION;LANGUAGE=en-US:Placeholder invite to secure attendee calendars.
***************
DTSTART;TZID=Eastern Standard Time:20211116T040000 DTEND;TZID=Eastern Standard Time:20211116T090000 UID:A42733D5-5F67-4C9C-98BF-CE993786DED3 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20211101T180910Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:2 LOCATION;LANGUAGE=en-US:TBD X-MICROSOFT-CDO-APPT-SEQUENCE:2 X-MICROSOFT-CDO-OWNERAPPTID:2119895472 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DISALLOW-COUNTER:FALSE BEGIN:VALARM DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M ACTION:DISPLAY END:VALARM END:VEVENT END:VCALENDAR
Alle antwoorden (1)
See workaround here https://support.mozilla.org/en-US/questions/1354438