Closed Bug 404487 Opened 17 years ago Closed 17 years ago

recurring event, open edit dialog via context menu -> no 'Editing a repeating item'-dialog

Categories

(Calendar :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: andreas.treumann, Unassigned)

Details

(Keywords: regression)

STEPS TO REPRODUCE:
===================

- create a recurring event
- select a single event of this rule
- open the context menu
- choose 'Edit Item'

RESULT:
=======

- the edit dialog comes up

EXPECTED RESULT:
================

- first the 'Editing a repeating item'-dialog should be visible.

REPRODUCIBLE:
=============

- always

mouse clicking a single event of this rule opens the 'Editing a repeating item'-dialog.
Flags: blocking-calendar0.8?
Let's mark this as wanted0.8+ for now. This may be elevated to blocking status
later in the game, but not now.
Flags: blocking-calendar0.8? → wanted-calendar0.8+
No regression. Sunbird 0.5 and Sunbird 0.7 show the same behavior.
For recurring events, I suggest replacing the "Edit Selected Event" menuitem with two items "Edit this occurrence" and "Edit all occurrences".

Perhaps these two should be separated in a submenu. It makes them a bit harder to navigate to, but on the other hand the user is forced to make a choice. If both appears directly in the topmost context menu between the many other menuitems, the user may not be aware that there are two edit options.
Works for me using Lightning 0.8pre (2007121503) with Thunderbird 2.0.0.12pre (20071214).

Works for me using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.12pre) Gecko/20071215 Calendar/0.8pre.
Verified with Lightning 2008012900 and Mozilla/5.0 (Windows; U; Windows NT 5.1;
pl; rv:1.8.1.12pre) Gecko/20080127 Calendar/0.8pre
Status: RESOLVED → VERIFIED
VERIFIED Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Lightning/0.8pre (2008012818) Thunderbird/2.0.0.9 ID:2007103104
Target Milestone: --- → 0.8
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.