Bugzilla

Looking at this more closely, I have some reservations.  I like Alex's design for a quick and lightweight popup as an improvement over the current hover/tooltip summary (comment 4), but I'm not sure that opening our current read-only summary dialog and requiring a second click to edit the item is a good idea.  We might be better off taking our time and implementing Alex's design rather than doing this intermediate step.  Or if we do want to do the intermediate step, I agree with comment 1 that there should be a preference to either enable the new behavior or restore the current behavior.

The biggest pain point we currently have is when you just want to view a repeating event, you open it but then are asked about editing just that event or all of them.  I think that's the most pressing UX problem to solve.

However, (with the current state of the implementation work), if you want to *edit* a repeating event you have to open the event in a summary dialog, then click the "Edit" button which opens a second dialog asking whether you want to edit just this event or all of them, and then click one of those options to open a third dialog for editing.  So while we're reducing the "view repeating event" flow from two dialogs to one, we are increasing the "edit repeating event" flow from two dialogs to three.

A fix for that problem: for repeating events, instead of an "Edit" button in the summary dialog, offer "Edit only this occurrence" and "Edit all occurrences" buttons.  That would remove the need for the "Edit Repeating Event" dialog, basically merging it into the summary dialog, which would then do that job.  Then editing a repeating event is back to two dialogs.

So, here's what I would propose:
- when opening a non-repeating event, show the edit event dialog (the current behavior)
- when opening a repeating event, show the read-only event dialog with "Edit only this occurrence" and "Edit all occurrences" buttons
- optionally add a pref to allow opening a non-repeating event in the read-only dialog with an "Edit" button to edit.

That solves the biggest UX problem while otherwise maintaining the current behavior, to reduce UI/UX churn, until we have time to implement Alex's design for a lightweight popup.

(Aside: another UI/UX question is that (with the current patch), when you open up an event, reminders are editable in that dialog but nothing else is.  Average user asks "why?".  Having reminders be editable makes sense with current uses of the summary dialog, but it might need some consideration if we're using it in this new way.)

Looking at this more closely, I have some reservations.  I like Alex's design for a quick and lightweight popup as an improvement over the current hover/tooltip summary (comment 4), but I'm not sure that opening our current read-only summary dialog and requiring a second click to edit the item is a good idea.  We might be better off taking our time and implementing Alex's design rather than doing this intermediate step.  Or if we do want to do the intermediate step, I agree with comment 1 that there should be a preference to either enable the new behavior or restore the current behavior.

The biggest pain point we currently have is when you just want to view a repeating event, you open it but then are asked about editing just that event or all of them.  I think that's the most pressing UX problem to solve.

However, (with the current state of the implementation work), if you want to *edit* a repeating event you have to open the event in a summary dialog, then click the "Edit" button which opens a second dialog asking whether you want to edit just this event or all of them, and then click one of those options to open a third dialog for editing.  So while we're reducing the "view repeating event" flow from two dialogs to one, we are increasing the "edit repeating event" flow from two dialogs to three.

A fix for that problem: for repeating events, instead of an "Edit" button in the summary dialog, offer "Edit only this occurrence" and "Edit all occurrences" buttons.  That would remove the need for the "Edit Repeating Event" dialog, basically merging it into the summary dialog, which would then do that job.  Then editing a repeating event is back to two dialogs.

So, here's what I would propose:
- when opening a non-repeating event, show the edit event dialog (the current behavior)
- when opening a repeating event, show the read-only event dialog with "Edit only this occurrence" and "Edit all occurrences" buttons
- optionally add a pref to allow opening a non-repeating event in the read-only dialog with an "Edit" button to edit it.

That solves the biggest UX problem while otherwise maintaining the current behavior, to reduce UI/UX churn, until we have time to implement Alex's design for a lightweight popup.

(Aside: another UI/UX question is that (with the current patch), when you open up an event, reminders are editable in that dialog but nothing else is.  Average user asks "why?".  Having reminders be editable makes sense with current uses of the summary dialog, but it might need some consideration if we're using it in this new way.)

Looking at this more closely, I have some reservations.  I like Alex's design for a quick and lightweight popup as an improvement over the current hover/tooltip summary (comment 4), but I'm not sure that opening our current read-only summary dialog and requiring a second click to edit the item is a good idea.  We might be better off taking our time and implementing Alex's design rather than doing this intermediate step.  Or if we do want to do the intermediate step, I agree with comment 1 that there should be a preference to either enable the new behavior or restore the current behavior.

The biggest pain point we currently have is when you just want to view a repeating event, you open it but then get a dialog that asks about editing just that event or all of them.  I think that's the most pressing UX problem to solve.

However, (with the current state of the implementation work), if you want to *edit* a repeating event you have to open the event in a summary dialog, then click the "Edit" button which opens a second dialog asking whether you want to edit just this event or all of them, and then click one of those options to open a third dialog for editing.  So while we're reducing the "view repeating event" flow from two dialogs to one, we are increasing the "edit repeating event" flow from two dialogs to three.

A fix for that problem: for repeating events, instead of an "Edit" button in the summary dialog, offer "Edit only this occurrence" and "Edit all occurrences" buttons.  That would remove the need for the "Edit Repeating Event" dialog, basically merging it into the summary dialog, which would then do that job.  Then editing a repeating event is back to two dialogs.

So, here's what I would propose:
- when opening a non-repeating event, show the edit event dialog (the current behavior)
- when opening a repeating event, show the read-only event dialog with "Edit only this occurrence" and "Edit all occurrences" buttons
- optionally add a pref to allow opening a non-repeating event in the read-only dialog with an "Edit" button to edit it.

That solves the biggest UX problem while otherwise maintaining the current behavior, to reduce UI/UX churn, until we have time to implement Alex's design for a lightweight popup.

(Aside: another UI/UX question is that (with the current patch), when you open up an event, reminders are editable in that dialog but nothing else is.  Average user asks "why?".  Having reminders be editable makes sense with current uses of the summary dialog, but it might need some consideration if we're using it in this new way.)