Wallet chip trigger: network shortLabel + mobile connected-state layout #186
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#186
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?
Summary
#140 follow-up (scope B): improve the connected trigger (not only dropdown rows). Audit notes from @Brouie on
WalletButton.tsx.Problems
<sm): chip shows only truncated4+4address; no balance/copy/explorer/network affordance on the trigger (LUNC line added in #140 — verify layout still works).Acceptance criteria
NETWORKS) alongside chain logo onsm+trigger.e2e/navigation.spec.tsif needed.skills/AGENTS_FRONTEND_WALLET_CHIP.md+AGENTS_FRONTEND_RESPONSIVE_HEADER.md.Relates to: #140
cc @Brouie
marked as related to #140
mentioned in issue #140
mentioned in commit
5198fbc499mentioned in commit
5fcd3ce007Implementation summary (merged to
main@5198fbc)Connected wallet chip trigger now shows the Terra network shortLabel (from
getNetworkBadgeCopy()) beside the chain logo fromsm:up via newWalletChipNetworkIndicator. Mobile keeps LUNC + truncated address on the chip; network text stays hidden on the trigger (icon + tooltip) so header width is preserved — copy/explorer/switch remain menu-first per #140 scope B.Docs / agent playbooks
Verification checklist
≥640px): connect wallet → chip shows Local (or Mainnet/Testnet for your build) next to chain icon<640px): chip shows LUNC +terra1…shorten; no visible network text on trigger; Environment ribbon still shows networkAddressRowcopy/explorer still work (#188); Esc / backdrop dismiss still work (#187)npm run test -- --run src/components/wallet/__tests__/WalletButton.test.tsxpassesnpx playwright test e2e/navigation.spec.ts --grep "GitLab #186"passes (needs LocalTerra +.env.local)@Brouie — please verify on your audit viewport(s); leaving the issue open until sign-off.
mentioned in commit
f81f620f6bmentioned in issue #185
qa cleared at source+test layer @PlasticDigits
verified
5198fbc/5fcd3ce.WalletChipNetworkIndicator.tsx — new component at src/components/wallet/. Chain logo always rendered, shortLabel via
hidden sm:inline(visible sm+ up, hidden on mobile). Falls back to title=" · " for the mobile tooltip. data-testid hooks present.WalletButton.tsx — imports the new indicator (line 10), renders it inside the trigger (line 69). Mobile chip still shows LUNC + 4+4 address via the sm:hidden right column (lines 63-68), no overlap with the new indicator.
docs/frontend.md — § "Connected wallet chip — network label & mobile layout" (line 91) covers the chip-vs-menu strategy.
skills/AGENTS_FRONTEND_WALLET_CHIP.md + skills/AGENTS_FRONTEND_RESPONSIVE_HEADER.md both present.
WalletButton.test.tsx — 8/8 passing (ran under #187). The #186 unit case "shows network shortLabel on the connected trigger" is green.
e2e/navigation.spec.ts — 3 Playwright cases under describe('Connected wallet chip network (GitLab #186)'):
source side complete. Playwright e2e + 1280/mobile/tablet viewport walk pending — same tunnel/YieldOmega conflict as #187, will run on next clean stack session.
Browser walk done — stack came up clean:
Unit tests 8/8 PASS at
5198fbc4/5fcd3ce0(ran under #187).Playwright e2e didn't get a clean run — QA blocks dev wallet via the public-IP guard, and the WSL setup can't reach the host-bound tunnels from headless Chromium. Browser walk covers the same surface. Will run the e2e on next clean stack session.
@PlasticDigits good to close.
mentioned in commit
be2d8644c1mentioned in issue #214
mentioned in merge request !829
mentioned in issue #292
mentioned in merge request !831
mentioned in commit
b023bd2b26mentioned in merge request !836
mentioned in commit
371985597ementioned in commit
e4d55e8eb4mentioned in issue #483
mentioned in merge request !1019
mentioned in issue #656
mentioned in issue #671
mentioned in merge request !1170