Open Bug 978570 (icaljs) Opened 8 years ago Updated 5 months ago

[meta] Enable ical.js by default

Categories

(Calendar :: ICAL.js Integration, task, P2)

Lightning 2.6

Tracking

(Not tracked)

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
Priority: -- → P2
Depends on: 978571
Depends on: 1081534
Depends on: 1082286
Depends on: 1103187
Depends on: 1115667
Depends on: 1117456
Blocks: 700827
Depends on: 1212914
Depends on: 1179783
Depends on: 1266797
Depends on: 1411530
Keywords: meta

We should make this happen for 76, and drop libical shortly after.

Type: defect → task
Depends on: 1643701
Depends on: 1659582

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.