The user interface for publishing is a bit poor. The feedback is pretty minor, and error reporting is also lacking. It could all be done much better.
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
Additionally, we should resolve the ambiguity between calendar/base/calendar-publish-dialog.xul and calendar/resources/publishDialog.xul. It seems the latter is being used for both lightning and sunbird, while the former is not even referenced. This should have happened in bug 293545. I think this doesn't require a separate bug, since a new publish dialog should live in base/content anyway. mvl, do you have a UI suggestion for the dialog?
Summary: Improve publish UI → Improve publish UI and unify the dialogs in calendar/base and calendar/resources
(In reply to comment #5) Usage of calendar-publish-dialog.xul was removed on purpose with Bug 323183. The Lightning publish code is not used anymore, see also Bug 293710. The obsolete files were just never removed from CVS. Bug 305526 exists to move the publish code used by Sunbird/Lightning from resources/ to base/ directory.
Assignee: nobody → mschroeder
Status: NEW → ASSIGNED
Assignee: mschroeder → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.