Skip to content

[ML 0.1/UI.04.11] - Validate full behaviour parity between Compose and legacy message list #10784

@rafaeltonholo

Description

@rafaeltonholo

Blocked by

Description

Once all wiring tickets are complete, a full parity validation is needed to confirm the Compose MessageListScreen behaves consistently with the legacy implementation across all interaction paths.

Acceptance Criteria

  • Message loading displays the same data as legacy.
  • Pull-to-refresh triggers sync and updates the list.
  • Footer "load more" works correctly.
  • Single message click opens the correct message/thread.
  • Swipe actions (all types) execute correctly.
  • Selection mode (enter, toggle, exit) works correctly.
  • Star/favourite toggle persists correctly.
  • Account indicator visibility is correct for unified folders.
  • No regressions in existing legacy behaviour.

Out of Scope:

  • Performance benchmarking.
  • UI polish or design changes.

Metadata

Metadata

Assignees

Labels

tb-teamTasks and features handled by project maintainerstype: taskGeneral tasks or to-dos

Type

Projects

Status

Planning

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions