Open Bug 2062000 Opened 3 months ago Updated 1 month ago

Implement Repeat subview shell

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:
Build the Repeat view inside the event dialog. Let users open it from the
recurrence row and return with Back without losing their unsaved changes.
This story builds the view's structure, not its repeat-rule editors.

Links:

Acceptance criteria:

  • Open Repeat from the main recurrence entry and provide Back to the main view.
  • Use the same fixed header and footer layout as the main dialog. Set focus
    appropriately on entry and restore it when the user goes Back.
  • Show the basic non-repeating and already-repeating states from the current draft.
  • Entering and leaving Repeat preserves draft values, changed-section tracking,
    validation results, and operation status.
  • Do not save from Repeat. Back returns to the main dialog, where its Save
    button handles saving.
  • Changing the dialog's event or session, or closing the dialog, exits Repeat.
    Its old controls must not change a newer draft.

Required implementation details:

  • Render through stable storeObserver selections of the current session's
    serializable draft. A session identifies one create or edit operation.
    Do not add getters that read the store directly.
  • Keep the active view in the dialog controller. Do not add a Redux slice just
    for temporary navigation state; shared navigation needs would be follow-up work.
  • Use the shared recurrence draft. Do not make a separate copy, reset it on
    navigation, or give the view its own recurrence data.
  • Keep calIEvent, recurrence API objects, live calendars, DOM nodes, and editor
    objects out of Redux and the observed data.
  • Leave preset and custom rule controls to Bugs 2061581 and 2061582.

Minimum test coverage:

  • Check entry, Back, focus on entry, and focus restoration.
  • Check non-repeating and already-repeating states from Redux updates.
  • Check fixed header/footer behavior and no direct Save.
  • Check navigation preserves draft values, changed sections, validation, and
    operation status.
  • Switch events or close the dialog while Repeat is open. Check it exits and
    old controls cannot change the newer draft.
  • Check no live platform objects enter Redux or observed values.
  • Run axe checks on displayed Repeat states where supported.

Out of scope:

  • Editing repeat rules, loading events, and implementing the shared draft/session.
  • Save transactions and saving events.
  • Changing the parent dialog's positioning.
Blocks: 2061581
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.