Closed Bug 2072471 Opened 1 month ago Closed 1 month ago

Thunderbird mangles vCard V4.0 REV timestamp invalidating vcard.

Categories

(Thunderbird :: Address Book, defect)

Thunderbird 155
defect

Tracking

(thunderbird_esr153 wontfix, thunderbird157 wontfix)

RESOLVED FIXED
158 Branch
Tracking Status
thunderbird_esr153 --- wontfix
thunderbird157 --- wontfix

People

(Reporter: alan, Assigned: mkmelin)

References

Details

Attachments

(1 external file)

Steps to reproduce:

Create a vcard in Migadu's web browser addressbook, sync with Thunderbird using carddav, modify a field in Thunderbird and sync. Change is not displayed in Migadu's addressbook, as the Vcard is no longer valid.

Actual results:

Migadu's web browser addressbook vcard implementation sets REV using YYYY-MM-DDTHH:mm:ssZ - for example 2026-09-14T10:15:20Z, which is compliant with ISO8601 format timestamp per the spec.

When Thunderbird updates the vcard it overwrites REV and the above example is now 2026-09-T4T10:1 which is not a valid timestamp.

Expected results:

Thunderbird should use a legitimate timestamp - preferably YYYY-MM-DDTHH:mm:ssZ to remove any ambiguity around timezone of timestamp.

The layout of the Thunderbird written timestamp suggests Thunderbird assumes the first 8 char are date, a T, and then next 6 char are time - irrespective of their actual values.

Component: Untriaged → Address Book

Ugh.

Assignee: nobody → mkmelin+mozilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: Thunderbird mangles vcard V4.0 REV timestamp invalidating vcard. → Thunderbird mangles vCard V4.0 REV timestamp invalidating vcard.
Target Milestone: --- → 158 Branch

Pushed by martin@humanoids.be:
https://hg.mozilla.org/comm-central/rev/8a1701710fcf
Don't mangle a vCard 4.0 REV timestamp given in the extended format. r=tobyp

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: