Open
Bug 978570
(icaljs)
Opened 7 years ago
Updated 16 days ago
[meta] Enable ical.js by default
Categories
(Calendar :: ICAL.js Integration, task, P2)
Tracking
(Not tracked)
NEW
People
(Reporter: Fallen, Unassigned)
References
(Depends on 7 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta)
This bug should gather blocking issues that keep us from switching to ical.js by default. This mostly means issues that restrict usability, i.e performance issues or major errors. More to come
Reporter | ||
Updated•7 years ago
|
Priority: -- → P2
Comment 1•2 years ago
|
||
We should make this happen for 76, and drop libical shortly after.
Type: defect → task
Comment 2•4 months ago
|
||
Concerning https://mail.mozilla.org/pipermail/tb-planning/2020-October/008030.html, if the plan is to switch to https://github.com/mozilla-comm/ical.js/, then somebody shall tackle now the problems reported for ical.js, as this will avoid later problems within Thunderbird.
As far as I know libical is very much modified within the Thunderbird source code, compared to upstream and upstream it has very few reported problems. (Or rather, compared to its usage, the reported problems have the nature of feature requests or uncertainty of how to read RFCs). Switching to upstream libical could be also a means to increase maturity by reducing IT burden.
You need to log in
before you can comment on or make changes to this bug.
Description
•