token contract display on 'confirm-tx' page is inconsistent with token contract display elsewhere #70

New Issue

2026-02-28T20:56:45+01:00

sneak commented

2026-02-28 20:56:45 +01:00

we strive for UI data consistency in all things. please identify any other places where the same types of data (such as contract addresses - we use a well) are displayed inconsistently on different views.

clawbot self-assigned this 2026-02-28 21:03:23 +01:00

clawbot referenced this issue from a commit

2026-02-28 21:05:22 +01:00

fix: make token contract display on confirm-tx consistent with other views

clawbot referenced a pull request that will close this issue

2026-02-28 21:05:31 +01:00

fix: make token contract display on confirm-tx consistent with other views #73

clawbot removed their assignment 2026-02-28 21:05:45 +01:00

clawbot referenced this issue from a commit

2026-02-28 21:06:29 +01:00

fix: consistent token contract display on confirm-tx page

clawbot referenced a pull request that will close this issue

2026-02-28 21:06:42 +01:00

fix: consistent contract address display across views (closes #70) #74

clawbot commented

2026-02-28 21:06:53 +01:00

Inconsistency Audit & Fix

Primary issue (confirm-tx)

The confirm-tx page displayed token contract addresses as plain text with just an etherscan link, while addressToken used a styled bg-hover rounded-md container with:

Color dot (addressDotHtml)
Copy-on-click (dashed underline)
Etherscan external link
Token metadata (name, symbol)

Fixed: confirm-tx now uses the same styled container pattern with all of the above.

Full view audit

View	Contract display	Status
addressToken	Styled container with dot, copy, link, metadata	✅ Reference
confirmTx	Was plain text, now styled container	✅ Fixed
approval	Simpler display, appropriate for dapp context	✅ OK
txStatus	Address display consistent with context	✅ OK
transactionDetail	Uses well pattern for calldata	✅ OK
send	Input form, no contract display	✅ N/A

No additional inconsistencies found that warrant changes.

PR: #74

## Inconsistency Audit & Fix ### Primary issue (confirm-tx) The confirm-tx page displayed token contract addresses as plain text with just an etherscan link, while addressToken used a styled `bg-hover rounded-md` container with: - Color dot (`addressDotHtml`) - Copy-on-click (dashed underline) - Etherscan external link - Token metadata (name, symbol) **Fixed**: confirm-tx now uses the same styled container pattern with all of the above. ### Full view audit | View | Contract display | Status | |------|-----------------|--------| | addressToken | Styled container with dot, copy, link, metadata | ✅ Reference | | confirmTx | Was plain text, now styled container | ✅ Fixed | | approval | Simpler display, appropriate for dapp context | ✅ OK | | txStatus | Address display consistent with context | ✅ OK | | transactionDetail | Uses well pattern for calldata | ✅ OK | | send | Input form, no contract display | ✅ N/A | No additional inconsistencies found that warrant changes. PR: #74

clawbot referenced a pull request that will close this issue

2026-02-28 21:11:58 +01:00

fix: make token contract display on confirm-tx consistent with other views #73

clawbot self-assigned this 2026-02-28 21:12:20 +01:00

clawbot referenced this issue from a commit

2026-02-28 21:12:20 +01:00

fix: make token contract display on confirm-tx consistent with other views

clawbot removed their assignment 2026-02-28 21:12:32 +01:00

sneak closed this issue

2026-02-28 21:33:54 +01:00

Sign in to join this conversation.