Support new VALARM properties (RFC 9074)
Categories
(Calendar :: Alarms, defect, P2)
Tracking
(Not tracked)
People
(Reporter: ljeloudev, Assigned: maxe)
References
(Blocks 1 open bug, )
Details
Attachments
(3 files)
Updated•14 years ago
|
Comment 2•14 years ago
|
||
Comment 5•14 years ago
|
||
Comment 7•14 years ago
|
||
Updated•14 years ago
|
Updated•14 years ago
|
Updated•12 years ago
|
Comment 10•12 years ago
|
||
Updated•12 years ago
|
Comment 11•12 years ago
|
||
Updated•11 years ago
|
Comment 12•11 years ago
|
||
Comment 13•11 years ago
|
||
Updated•9 years ago
|
Comment 14•8 years ago
|
||
Updated•5 years ago
|
Comment 15•5 years ago
|
||
Updated•5 years ago
|
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 months ago
|
| Assignee | ||
Comment 16•3 months ago
|
||
To be clear, it was a draft for a long time but was properly published in 2021: https://datatracker.ietf.org/doc/html/rfc9074
| Assignee | ||
Comment 17•3 months ago
|
||
I do not see any open issue or pull request on https://github.com/kewisch/ical.js, which is the prerequisite to any possible work here.
Please give some advice on the appropriate order of implementation and review process between ical.js and Thunderbird to me or any other potential contributor here.
Comment 18•3 months ago
|
||
In theory ical.js should support VALARM extensions, as it supports arbitrary components. There were some dependencies back with the wip patch since libical needed specific design data. You should be able to do the remainder of the work in Thunderbird code. From faint memory I believe the main issues back then why I didn't complete this was migration work. We have a bunch of alarms with the x-moz properties, so the old system kind of still needs to work.
Do you have any changes for ical.js in mind that I missed?
| Assignee | ||
Comment 19•3 months ago
•
|
||
Draft attempt.
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
| Assignee | ||
Comment 20•3 months ago
•
|
||
Sorry for the amount of e-mails you may have received by now.
No matter whether my patch will make it or not, I propose a lazy migration where our old custom X-MOZ- attributes stay untouched unless the date/time of an event or alarms attached to it are touched, editing the description of an event should not silently upgrade to VALARM.
Backwards compatibility with older Thunderbird releases cannot be a concern forever, afaik there are no other users of the X-MOZ- style attributes not capable of also parsing modern VALARM.
For clarity, I am talking about X-MOZ-LASTACK, X-MOZ-SNOOZE-TIME as well as X-MOZ-SNOOZE-TIME-*.
Updated•2 months ago
|
Description
•