adamkoa Reporter
	Description • 9 years ago

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Maxthon/4.4.5.1000 Chrome/30.0.1599.101 Safari/537.36

Steps to reproduce:

Subscribe to a Google calendar.


Actual results:

A reoccuring event is displayed on a wrong date - namely: scheduled on every month 12th day but displayed on the first day.
If I open the event and select all occurrences the dates are correct (12th) but if I open the actual event the date is incorrect (1st) and when I scroll to another mot still displaying in the wrong date.

Naturally, when I check it on Goggle's online calender its on its place.
Morever, it was correctly showed on preveious builds, just the last few showed up this error.


Expected results:

Display the event on a correct date.

	Decathlon
	Comment 1 • 9 years ago

Could you please export in ics format the calendar with the event (menu Events and Tasks -> Export...), edit the ics file (cut the others events, leave the timezone section and modify every reference to personal information) and attach here the text?
There are errors in the console (CTRL+Shift+j)?

	adamkoa Reporter
	Comment 2 • 9 years ago

The problematic event export.

	adamkoa Reporter
	Comment 3 • 9 years ago

Its interesting that the export contains two times the same event name, so I've included both in the export file.

The console does not contains any error related to the calendat, but will check regularly.

	Decathlon
	Comment 4 • 9 years ago

This should be a duplicate of bug 1103187 that is fixed upstream on ical.js but the changes have not been imported on Lightning yet (see bug 1115667).
As confirmation, you should have the preference "calendar.icaljs" set to true, please check in Tools->Options->Advanced->Config Editor if this is the case.

Depending on your versions of Thunderbird and Lightning, setting that preference to false (i.e. enabling libical instead of ical.js) might not work because of an incompatibility with binary components.
The latest versions (since the 22nd of May?) work fine.

	adamkoa Reporter
	Comment 5 • 9 years ago

I've checked the option and it was set on the default vaule which was true - so I've changed it to false and restarted Daily and the event appeared on the right place, meaning libical works correctly with the latest Daily build.

After that I've pulled the latest ical.js and replaced the original one (simple file replace), but the calendar plugin lost all of it entries and continous 9% cpu usage was the result - I revert everything.

So, which versions are recommended for Daily till bug 1103187 resolved in Lighning 3.3?

	Decathlon
	Comment 6 • 9 years ago

(In reply to adamkoa from comment #5)
> So, which versions are recommended for Daily till bug 1103187 resolved in
> Lighning 3.3?

Here did you mean 4.3?

Currently ical.js has been enabled by default because of another bug. Maybe it will stay in that way for experimental reasons on the nightly channel, but here I could be wrong, I don't know precisely what has been planed.
Anyway, whichever version you use, at the moment libical is always preferable compared to ical.js even though there are few bugs that ical.js corrects, but there are many others that it introduces (even with bug 1115667 applied), along with some performance issue.

If you have to use ical.js for some reason, you could apply the patch attached in bug 1103187 by editing manually the file ical.js.

	adamkoa Reporter
	Comment 7 • 9 years ago

Ups, sorry, typo :)
I use 4.3 and no reasons to force use ical.js, I'm just testing it.

Thanks for pointing to the original ticket, next time I'll use better search terms to check existing issues.