Open Bug 2061581 Opened 3 months ago Updated 1 month ago

Implement preset recurrence choices

Categories

(Calendar :: Calendar Frontend, task)

task

Tracking

(Not tracked)

People

(Reporter: arschmitz, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Whiteboard: [calendar-ui-create-edit])

Summary:
Let users choose a common repeat schedule in the Repeat view. Store the choice
as a rule in the draft, which holds unsaved values. Apply it to the event only
when Save succeeds.

Links:

Acceptance criteria:

  • Offer Daily, Daily on weekdays, Weekly, Every 2 weeks, Monthly, Quarterly,
    and Yearly where supported by existing Calendar recurrence behavior.
  • Show the preset selected in the current draft.
  • Selecting a preset changes only the recurrence section of the draft.
  • Save and reload the selected rule through existing Calendar recurrence APIs
    without changing its meaning. Preserve Undo, Redo, and notification behavior
    for successful create and edit transactions.
  • Adding or removing recurrence stays with Bug 2061580.
  • After leaving Repeat or switching events, an old preset selection must not
    change a newer draft.

Required implementation details:

  • Render stable storeObserver selections for the current session, which
    identifies one create or edit operation. Do not add store-reading getters.

  • Send one typed recurrence-only update with a plain, serializable rule.
    Do not create, retain, or modify live recurrence API objects on selection.

  • Keep calIRecurrenceInfo, live rule objects, calIEvent, live calendars, input
    elements, and editor objects out of Redux, actions, and the draft.

  • The field-owned Save serializer converts the plain rule using existing
    recurrence APIs. The create/edit Save controllers perform the transaction.

  • Reject old selections after session replacement or subview exit.

  • Use the row enabled state from Bug 2061214. Convert a rule only when Repeat
    is enabled. When disabled, create no recurrence and remove old recurrence
    from the event copy on edit. Keep the retained draft rule unchanged.

Minimum test coverage:

  • Check each supported preset and its displayed selected state.

  • Check recurrence-only updates and no live platform objects in Redux or actions.

  • Save and reload every preset; check that its repeat rule is preserved.

  • Check the existing Undo, Redo, and notification behavior through Save.

  • Check Add/Remove remains connected to Bug 2061580's behavior.

  • Leave Repeat or switch from A to B, then check that old selections cannot
    change the newer draft.

  • Run axe checks on displayed preset controls where supported.

  • Choose a preset, turn Repeat off, then on. Check that the preset remains.
    Save while off must omit recurrence for a new event and remove it on edit.

Out of scope:

  • Basic Add/Remove, custom recurrence fields, and prompts about which
    occurrences to change.
  • Implementing the shared draft model.
  • Direct event changes or saving outside the create/edit Save transaction.
Blocks: 2061582
Depends on: 2062000
No longer depends on: 2061580
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.