Open
Bug 304465
Opened 19 years ago
Updated 2 years ago
bogus events should be reported to system console on construction
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
NEW
People
(Reporter: dmosedale, Unassigned)
Details
When reading in a calendar that contains bogus events (eg end-time before start-time), these events should be reported to the console using Components.utils.reportError. Conceivably the user could be prompted about what to do with such events. Without a prompt, though, we should preserve them in the interest of not losing extant (though corrupt) data.
Comment 1•19 years ago
|
||
Unfortunately, I do not have cycles to work on Calendar stuff these days (just as it's getting to the good part!), so I am a bad owner for these bugs. To delete the tragically-large chunk of bugspam, search for gregorianabdication.
Assignee: shaver → nobody
Updated•17 years ago
|
Version: Trunk → unspecified
Comment 2•15 years ago
|
||
We already report unparseable events on the error console, not sure how we handle parseable but wrong events (i.e end before start date) though. Given we have a few bugs open on the activitiy manager, maybe we can close this bug? Or should we create a calendar activity manager tracker metabug and make all these bugs block it?
Updated•15 years ago
|
Whiteboard: [error handling]
Updated•12 years ago
|
Whiteboard: [error handling]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•