Closed
Bug 463275
Opened 16 years ago
Closed 14 years ago
Edit Recurrence dialog shows wrong rule when editing event
Categories
(Calendar :: Dialogs, defect)
Calendar
Dialogs
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b7
People
(Reporter: ssitter, Assigned: Fallen)
Details
(Whiteboard: [not needed beta][no l10n impact])
Attachments
(2 files)
514 bytes,
text/plain
|
Details | |
2.53 KB,
patch
|
ssitter
:
review-
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081105 Calendar/1.0pre (BuildID: 20081105110610)
Steps to Reproduce:
1. Start Sunbird with clean profile
2. Import the attached testcase that was taken from Bug 365034
3. Open the event for editing, choose "Edit all occurrences" when prompted
4. Choose "Custom..." from the Repeat dropdown menu
Actual Results:
Recurrence summary in the Edit Event dialog correctly shows "Occurs every December 26 effective 12/26/2006.". But in the Edit Recurrence dialog the selection is incorrectly set to "Annually. Every [1] [January|v]".
Expected Results:
Correct recurrence rule is pre-selected in the Edit Recurrence dialog.
Error Console doesn't report anything.
Updated•16 years ago
|
Flags: blocking-calendar1.0+
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → philipp
Assignee | ||
Comment 1•16 years ago
|
||
This patch takes care of correctly loading the recurrence and also modifies the saving behavior. I'm a bit unsure if this is user-friendly though:
* Originally, we used to compose a rule BYMONTH=12;BYMONTHDAY=26 if dec 26 was
selected
* Now, when the recurrence dialog is opened and the user enters the same month
and day as the item starts on, we compose a rule BYMONTH=12.
- When the user changes the start date, the recurrence details get updated
As an alternative, we could just stay with the old behavior and modify the recurrence rule. This could be bad w.r.t iTIP/iMIP though.
Attachment #358602 -
Flags: review?(ssitter)
Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs review]
Assignee | ||
Updated•16 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 2•16 years ago
|
||
Comment on attachment 358602 [details] [diff] [review]
Fix - v1
The changes when loading the event looks OK. The changes when saving the event are not required in my opinion, as already discussed on IRC. With or without the change there are recurrence rules that get changed on save although the user changed nothing in the recurrence dialog. I'd keep the current behavior to ensure consistency with the previous releases.
Updated•16 years ago
|
Whiteboard: [needs review] → [needs review][not needed beta][no l10n impact]
Updated•16 years ago
|
Whiteboard: [needs review][not needed beta][no l10n impact] → [not needed beta][no l10n impact][needs review]
Reporter | ||
Updated•16 years ago
|
Attachment #358602 -
Flags: review?(ssitter) → review-
Reporter | ||
Comment 3•16 years ago
|
||
Comment on attachment 358602 [details] [diff] [review]
Fix - v1
I'd give r+ for the load changes but the save changes are still under discussion. Philip said about three weeks ago on IRC that an updated patch will be posted after discussion. Denying review request for now.
Reporter | ||
Updated•16 years ago
|
Whiteboard: [not needed beta][no l10n impact][needs review] → [not needed beta][no l10n impact][needs updated patch]
Updated•16 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Updated•16 years ago
|
Component: General → Dialogs
Updated•16 years ago
|
QA Contact: general → dialogs
Assignee | ||
Comment 4•14 years ago
|
||
I've decided to take the load changes only and will take the r+ from comment 3 :-)
Assignee | ||
Comment 5•14 years ago
|
||
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/c93871cba778>
-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Trunk
Assignee | ||
Comment 6•13 years ago
|
||
This bug was also pushed to comm-beta and comm-aurora, likely during the last merge.
Target Milestone: Trunk → 1.0b6
Updated•12 years ago
|
Whiteboard: [not needed beta][no l10n impact][needs updated patch] → [not needed beta][no l10n impact]
You need to log in
before you can comment on or make changes to this bug.
Description
•