Closed
Bug 278152
Opened 20 years ago
Closed 17 years ago
A relative calendar path causes an ugly error when you try to publish.
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 305527
People
(Reporter: brettk, Unassigned)
Details
If the user's local calendar is specified with a relative path (I specified mine relatively to my home directory), an error is emitted when trying to publish because nsLocalFile.initWithPath, which is called from calendar/jslib/filesystem.js:initPath, expects a fully qualified path name, and returns NS_ERROR_FILE_UNRECOGNIZED_PATH if this isn't the case. This error is then propagated up and ends up in an alert box with an ugly error message and a simple numeric error code... quite opaque. :) Suggested Solution: convert the path to an absolute one when the user is initially entering their calendar file name in the file dialog. At minimum, checking the type of exception and cleaning up the error box would help. BTW, I didn't know exactly where to post the bug, so I picked General.
Updated•19 years ago
|
QA Contact: gurganbl → general
Comment 1•18 years ago
|
||
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Updated•17 years ago
|
Whiteboard: [qa discussion needed]
This is an issue where the publishing dialog needs to be drastically improved. Duping against the appropriate bug for this.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Whiteboard: [qa discussion needed]
You need to log in
before you can comment on or make changes to this bug.
Description
•