Active nav item has no visual distinction (current page is not indicated in header) #137
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic#137
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue Summary
The header navigation (Swap, Pool, Limits, Trade, Charts) shows no active/selected state for the currently loaded route. All nav items look identical regardless of which page the user is on. A user cannot tell at a glance which section of the app they are in.
Reproduction Steps
http://127.0.0.1:3000/swap, observe the Swap nav item/trade, observe the Trade nav item/limits,/pool,/charts, repeat observationExpected Behavior
The nav item corresponding to the current route should have a distinct visual treatment, underline, highlight, filled background, bold weight, or color change so the user always knows where they are in the app.
Actual Behavior
All nav items render identically on every route. No active, selected, or current-page indicator is applied to the matching nav item. The user has no visual anchor for their current location.
Environment Details
localterra(local Docker)VITE_NETWORK=local npm run devWallet / Device Details
Screenshots
swap
trade
limits
Severity / Impact
P2 Polish. No functionality is broken but the missing active state is a standard navigation affordance expected on every web app. Without it, users, especially CEX migrants unfamiliar with the layout lose their orientation anchor. Affects all routes. Found under W1-C1 (Global chrome; Display dimension).
cc: @PlasticDigits
mentioned in issue #116
mentioned in commit
38f439f549@totdking — fix pushed for verification.
what changed
.app-nav-link-activeCSS rule existed but its values were too faint to read as visually distinct — 8% / 2% gradient opacity on background, 12% opacity on border-color. hover state used a real background color (var(--control-surface-hover)) plus translateY transform, so hover read STRONGER than active.bumped to use existing design tokens at full visibility:
var(--accent-surface)(real orange tint, matches the existing accent surface convention)rgba(255, 168, 77, 0.45)— 4× previous opacityinset 0 -2px 0 var(--accent)— bottom underline using the accent color, the canonical "you are here" nav cuefunctional logic untouched —
Layout.tsx:120already correctly applies the active class via React Router NavLinkisActiveprop. CSS-only visibility fix.scope: covers all 5 selectors sharing the active rule (
.app-nav-link-active,.app-footer-theme-button-active,.app-mobile-link-active,.app-mobile-more-active,.network-badge-active).verification needed
fix/glab-137-active-nav-indicator38f439fhow to verify
git checkout fix/glab-137-active-nav-indicatorcd frontend-dapp && npm run devverification gate (already passing on my side)
tsc -bcleannpm run test:unit— 315/315 PASS (43 files)npm run lint— 0 errors. 3 pre-existing warnings onLimitOrdersPage.tsx(untouched by this fix)ping when verified, i'll open the MR after your sign-off.
@totdking Please verify so we can close
mentioned in commit
a474f995ddverified and is ready for close
cc: @PlasticDigits & @Brouie
qa cleared, good to close @PlasticDigits