Closed
Bug 283401
Opened 20 years ago
Closed 20 years ago
Can't move to future/past months in calendar while editing an event.
Categories
(Calendar :: General, defect)
Calendar
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 216959
People
(Reporter: schussman, Assigned: mostafah)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
When editing an event, the main calendar is frozen. It is sometimes helpful to
see what is going on in future or past months while creating the new event.
So if I need to know something about past and future months while creating an
event, I have to cancel that event creation, write down on paper all the
relevant information from the other months, and then go back and re-enter the
new event information.
Reproducible: Always
Steps to Reproduce:
1. In the Month view, double click on a day to bring up the "New Event" dialog.
2. Without closing the "New Event" dialog, bring mouse focus back to the main
calendar window.
3. Click on any of the previous/next month buttons.
Actual Results:
Nothing
Expected Results:
The main window should continue to behave the way it does when the "New Event"
dialog is not there.
Alternative workaround: save the partially edited event (click ok), navigate to
the other month, then reopen the partially edited event (visible in the event
listing above the main grin, at least with an appropriate filter like All Events).
Comment 2•20 years ago
|
||
Reporter:
This looks like another way of saying bug 216959. Please look at that bug,
and if you agree that this one is a duplicate, please mark it as such.
Reporter | ||
Comment 3•20 years ago
|
||
*** This bug has been marked as a duplicate of 216959 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Comment 4•19 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in
before you can comment on or make changes to this bug.
Description
•