Closed
Bug 367216
Opened 18 years ago
Closed 18 years ago
edit events & tasks incorrectly display details as blanks the first time or when clicking 'More >>"
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 367184
People
(Reporter: pi, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060915 Firefox/1.5.0.7 (Swiftfox)
Build Identifier: 2007011603
All of the details (description, attendees, url, status, etc) are incorrectly empty the first time you edit an event or task (or when you click 'More >>' while editing).
Reproducible: Always
Steps to Reproduce:
1. right click to and create new event (task)
2. click on 'More >>'
3. Fill out all of the details and click 'Ok'
4. right click on this event (task) and select 'Edit Event' ('Edit Task')
5. click 'More >>' if needed
Actual Results:
All of the details (description, attendees, url, status, etc) are incorrectly empty the first time you do this. Seems to be a problem the first time and/or when you click on 'More >>' to edit event/task's full details. Hitting 'Cancel', and 'Edit Event/task' again properly displays previously entered details. Hitting 'Ok', instead of 'Cancel' wipes out details entered in step 3 above.
Expected Results:
All of the details filled out in 3. should remain there.
Can also reproduce by clicking 'Less <<', then 'Cancel', then 'Edit Event/Task' again, and 'More >>' again.
(Also, you have to resize the 'Edit Event' / 'Edit Task' after hitting 'More >>', though this should probably be a seperate and more cosmetic bug).
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a2pre) Gecko/20070116 Calendar/0.6a1
Comment 1•18 years ago
|
||
Duplicate of or related to Bug 367184?
Comment 2•18 years ago
|
||
Reporter, do you see any error message in "Tools > Error Console"?
| Reporter | ||
Comment 3•18 years ago
|
||
same error messages as in Bug 367184, marking as duplicate
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•