Place Limit functionality duplicated across /trade and /limits tabs with no distinction communicated to the user #129

Closed
opened 2026-05-04 17:19:56 +00:00 by totdking · 3 comments
totdking commented 2026-05-04 17:19:56 +00:00 (Migrated from gitlab.com)
No description provided.
totdking commented 2026-05-04 17:25:00 +00:00 (Migrated from gitlab.com)

Issue Summary

The Place Limit form appears on both the /trade page (embedded in the Order Ticket panel) and the /limits page (as a standalone surface). There is no explanation in the UI of why the functionality exists in two places or whether there is any difference between them. This creates ambiguity for traders navigating between the two tabs.


Reproduction Steps

  1. Complete full local setup and connect Station wallet
  2. Navigate to /trade — observe the Order Ticket panel on the right includes Place Limit, Cancel Limit, and Your Placements
  3. Navigate to /limits — observe a standalone page with the same Place Limit and Cancel Limit sections
  4. Note there is no UI copy, tooltip, or contextual hint explaining the relationship between the two surfaces

Expected Behavior

Either:

  • The two surfaces serve distinct purposes, in which case the UI should clearly communicate the difference (e.g. /trade for in-context limit orders alongside the book and chart; /limits as a lightweight standalone tool), or
  • One surface is redundant and should be removed or consolidated

In either case, a trader should never have to guess whether the two Place Limit forms are equivalent or distinct.


Actual Behavior

Both /trade and /limits present functionally identical Place Limit and Cancel Limit forms with no label, tooltip, or description distinguishing them. A trader navigating both tabs has no signal as to which to use or whether submitting from one differs from submitting from the other.


Environment Details

Field Value
OS macOS (Apple M1 Pro, 14-inch)
Browser Google Chrome (desktop)
Network localterra (local Docker)
Frontend VITE_NETWORK=local npm run dev
Indexer Running (make indexer-dev)

Screenshots

See attached screenshots of /trade (Order Ticket panel with Place Limit) and /limits (standalone Place Limit page) showing the duplicated form layout.

/limits

image.png{width=900 height=545}

/trade

image.png{width=900 height=545}


Severity / Impact

No functionality is broken, but the duplication creates unnecessary cognitive load and may lead traders to distrust the interface or avoid one surface entirely. Flagged as a product clarity issue per QA standards, technically expected behaviour that still causes user-facing confusion.

### Issue Summary The Place Limit form appears on both the `/trade` page (embedded in the Order Ticket panel) and the `/limits` page (as a standalone surface). There is no explanation in the UI of why the functionality exists in two places or whether there is any difference between them. This creates ambiguity for traders navigating between the two tabs. --- ### Reproduction Steps 1. Complete full local setup and connect Station wallet 2. Navigate to `/trade` — observe the Order Ticket panel on the right includes Place Limit, Cancel Limit, and Your Placements 3. Navigate to `/limits` — observe a standalone page with the same Place Limit and Cancel Limit sections 4. Note there is no UI copy, tooltip, or contextual hint explaining the relationship between the two surfaces --- ### Expected Behavior Either: - The two surfaces serve distinct purposes, in which case the UI should clearly communicate the difference (e.g. `/trade` for in-context limit orders alongside the book and chart; `/limits` as a lightweight standalone tool), or - One surface is redundant and should be removed or consolidated In either case, a trader should never have to guess whether the two Place Limit forms are equivalent or distinct. --- ### Actual Behavior Both `/trade` and `/limits` present functionally identical Place Limit and Cancel Limit forms with no label, tooltip, or description distinguishing them. A trader navigating both tabs has no signal as to which to use or whether submitting from one differs from submitting from the other. --- ### Environment Details | Field | Value | |-------|-------| | OS | macOS (Apple M1 Pro, 14-inch) | | Browser | Google Chrome (desktop) | | Network | `localterra` (local Docker) | | Frontend | `VITE_NETWORK=local npm run dev` | | Indexer | Running (`make indexer-dev`) | --- ### Screenshots > See attached screenshots of `/trade` (Order Ticket panel with Place Limit) and `/limits` (standalone Place Limit page) showing the duplicated form layout. /limits ![image.png](/uploads/07a7671ebbd89aef4eb07245215e9131/image.png){width=900 height=545} /trade ![image.png](/uploads/cd64c3da675cf6647c7dcb40dc1a7ccc/image.png){width=900 height=545} --- ### Severity / Impact No functionality is broken, but the duplication creates unnecessary cognitive load and may lead traders to distrust the interface or avoid one surface entirely. Flagged as a product clarity issue per QA standards, technically expected behaviour that still causes user-facing confusion.
Brouie commented 2026-05-05 23:55:34 +00:00 (Migrated from gitlab.com)

mentioned in issue #133

mentioned in issue #133
PlasticDigits (Migrated from gitlab.com) closed this issue 2026-05-06 09:21:46 +00:00
totdking commented 2026-05-07 17:32:42 +00:00 (Migrated from gitlab.com)

mentioned in issue #116

mentioned in issue #116
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
code/cl8y-dex-terraclassic#129
No description provided.