Skip to content

Frontend UX: add transaction-detail slide-over with stepwise lifecycle timeline #503

@CMI-James

Description

@CMI-James

Background

Users need a clearer way to inspect transaction progress and failure context without leaving the current surface or losing page context.

Feature Focus

Add a transaction-detail slide-over with a stepwise lifecycle timeline.

Where to Implement (Exact Targets)

  • apps/web/src/components/transactions/*
  • apps/web/src/pages/*
  • apps/web/src/styles/*
  • apps/web/src/tests/*

What to Implement

  • Add a slide-over panel that opens from transaction lists and summary cards.
  • Render a lifecycle timeline showing submission, confirmation, indexing, and any failure or retry steps.
  • Include compact metadata such as network, hash, timestamps, and retry state.
  • Preserve keyboard support, focus trapping, and close behavior.

Interface / Endpoint / Method Details

  • Reuse existing transaction models and route state where available.
  • Support both successful and failed transaction histories.
  • Keep the component resilient to partially available backend data.

Acceptance Criteria

  • Users can inspect transaction details without navigating away from the current page.
  • The timeline meaningfully distinguishes happy-path and failure-path states.
  • The slide-over is responsive and accessible.

Required Tests

  • Interaction tests for open, close, and focus-return behavior.
  • Rendering tests for successful, failed, and partially populated transaction records.

Definition of Done

  • Transaction detail slide-over is implemented and wired into at least one transaction surface.
  • Timeline behavior and accessibility are covered by tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrontendFrontend functionality workHighHigh complexityStellar WaveStellar Wave initiativeenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions