Open
Bug 332754
Opened 18 years ago
Updated 2 years ago
Undo/Redo can fail if called before the provider has a chance to process the previous change
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
NEW
People
(Reporter: jminta, Unassigned)
Details
Follow-up from Bug 325477. Because undo/redo depends on getting back the added event (it will be slightly modified during the addItem process) before it can actually perform an undo or redo action, there is a non-zero window of time during which an undo or redo can be attempted, but fail. Caching-calendars will probably help significantly with this.
|
||
Comment 1•18 years ago
|
||
The bugspam monkeys have struck again. They are currently chewing on default assignees for Calendar. Be afraid for your sanity!
Assignee: base → nobody
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•