REPRODUCTION: ============= - start thunderbird with wrong proxy settings - cancel the login dialogs of all remote calendars - change this settings to the correct settings - go to the calendars tabpage and choose 'reload remote calendars' - reload the calender view, all calendars are visible - go to the agenda or todo tabpage -> there are no entries RESULT: ======= - No entries in agenda and todo tabpage after 'reload remote calendars' EXPECTED RESULT: ================ - 'reload remote calendars' refreshes the agenda and todo tabpage REPRODUCIBLE: ============= - always
Same underlying problem as in Bug 352255?
js console output Error: this.selectedDay has no properties Source File: chrome://calendar/content/calendar-decorated-week-view.xml Line: 187
I can confirm this using Lightning 0.3.1 - I refreshed my network calendar, which was slightly modified from when I originally set the calendar up in Lightning, but I had to restart Thunderbird to get the changes to show up in the Agenda. My steps to reproduce: 1.) Import a remote calendar. 2.) Change an item on the remote calendar (in my case, delete an item and replace it with two others on the same day). 3.) Reload the remote calendar. 4.) The Agenda tab will show only the old, deleted item; the new items will not be listed. 5.) Restart Thunderbird - the old item will be gone and the new items will be in place. I have been able to reproduce this problem on demand.
This bug exists in Thunderbird 184.108.40.206-Lightning20071122 configuration too. The reload doesn't refresh the task-list, the changes in the remote calendar takes effect only after restart.
Summary: [Proto] No refresh in agenda and todo tabpage after 'reload remote calendars' → No refresh in agenda and todo tabpage after 'reload remote calendars'
Andreas, can you still reproduce this issue?
No response for a while now, closing INCOMPLETE. Please reopen if you can reproduce or answer any unanswered questions.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.