Mobile (390x844): Canonical fee sinks panel truncates addresses with no scroll, copy, or expand affordance #93
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#93
Loading…
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
At mobile viewport (390x844, iPhone 12 Pro preset via DevTools), the Canonical fee sinks (read-only) panel that appears on every page truncates each sink address mid-string with no scroll affordance, no tap-to-expand, no copy-to-clipboard button, and no
text-overflow: ellipsisindicator that more content exists. Users on real phones cannot read or verify the sink addresses.Repro
282eb62localhost:5173/(or any route — panel is global)Observed
Each of the 5 sink rows clips the hex address at the panel's right edge:
0x5FC8d32690cc91D4c39d9d3abcBD16989F8...[clipped]0x000000000000000000000000000000000000...[clipped]0xCf7Ed3AccA5a467e9e704C703E8D87F6341...[clipped]0xa513E6E4b8f2a923D98304ec87F64353C4D...[clipped]0x8A791620dd6260079BF849Dc5567aDC3F2F...[clipped]Full addresses cannot be visually verified, copied, or parsed. No interaction surfaces the truncated portion.
Why it matters
The canonical fee sinks panel is the trust surface for "where does my CL8Y go" — users want to verify sink addresses match the spec / docs / their own audit notes. On mobile (where most retail will land post-TGE), this critical transparency surface is functionally broken because the addresses are unreadable.
Suggested resolution options
0x5FC8...5707) and provide tap-to-expand or tap-to-copy. Standard wallet UX pattern.Option 1 plus option 3 (middle ellipsis + copy button) is the strongest combo — matches what every wallet / explorer does for hex addresses on mobile.
Scope
This is a mobile-only display issue. Desktop renders the full address line correctly. Same panel, same component (looks like a shared footer surface across all routes), so a single-component fix lands everywhere.
Severity
P2-medium. Not a launch-blocker (data is technically correct, not user-tampering surface), but is a real polish gap on the most-trust-sensitive panel for mobile users.
Reference screenshot
Captured during F-13 mobile walkthrough as part of #38 deferred items.
cc @PlasticDigits
mentioned in issue #95
mentioned in issue #38
mentioned in commit
787e586718Implemented #93 on `main` (commit
3480d53).What changed
Verify (for @brouie)
Leaving issue open per request.
mentioned in issue #100
mentioned in commit
ca2aaffdd6Partial verification on
3480d53(carried into243e2a0).Item 5: Vitest guards green
Item 3 partial: addresses match
cast callVerified
feeRouter.sinks(0..4)against the live deployment at0xA51c1fc2f0D1a1b8494Ed1FE312d7C3a78Ed91C0:0x5FC8d32690cc91D4c39d9d3abcBD16989F8757070x000000000000000000000000000000000000dEaD0xCf7Ed3AccA5a467e9e704C703E8D87F634fB0Fc90xa513E6E4b8f2a923D98304ec87F64353C4D5C8530x8A791620dd6260079BF849Dc5567aDC3F2FdC3180xCf7Ed3Ac...0Fc9) matchesPodiumPoolincontracts/deployments/local-anvil-registry.json.0x8A791620...DC318) matchesRabbitTreasuryin registry +VITE_RABBIT_TREASURY_ADDRESSinfrontend/.env.local.cc @PlasticDigits
mentioned in issue #217
mentioned in issue #232