Closed
Bug 367174
Opened 19 years ago
Closed 19 years ago
Disable function for calendar in lightning is broken
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: omar.bajraszewski, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier:
Disabling calendar causes nothing: events are visible in main view
Reproducible: Always
Steps to Reproduce:
1.Create two or three calendars
2.Create an event for first calendar on the list
3.Disable the calendar
Actual Results:
Event is still visible
Expected Results:
Event should disappear after disabling the calendar
Thunderbird version 2 beta 1 (20070113)
Lightning build 2007011605
WCAP enabler build 20070116
Comment 1•19 years ago
|
||
Works for me using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/20070116 Thunderbird/2.0b1 with Lightning/0.4a1 (2007011605) and three storage calendars.
Could this be caused by one of the errors you experienced and reported in earlier bugs?
| Reporter | ||
Comment 2•19 years ago
|
||
Well, yes. I tried to delete the events that I had created for reporting the previous bugs. It wasn't possible- see bug 367172. So I tried to disable the calendar and I noticed the events didn't disappear
Comment 3•19 years ago
|
||
Omar, can you reproduce this with a clean profile and new calendars or should we resolve this bug as WFM?
| Reporter | ||
Comment 4•19 years ago
|
||
I can't reproduce it. It was caused by bug 367172 which is marked as WFM now. I need to re-check that bug to verify disable function for calendar and it's impossible at the moment----> another function for proto is broken. I can't create recurring events.
Comment 5•19 years ago
|
||
So mark as WFM?
| Reporter | ||
Comment 6•19 years ago
|
||
It can't be reproduced at the moment--->WFM
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•