fix(frontend): allow Resolved addresses label column to fit long env keys (GitLab #214) #391
No reviewers
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!391
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/glab-214-resolved-addresses-overflow"
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?
Resolves #214.
The Resolved addresses block on both agent card surfaces (AGENT CARD: TIMECURVE SIMPLE and AGENT CARD: FOR AGENTS ONLY) was overlapping label text into the address column on long env var labels like VITE_REFERRAL_REGISTRY_ADDRESS and VITE_KUMBAYA_TIMECURVE_BUY_ROUTER.
Root cause: .app-footer-agent__dl in index.css capped the label column at minmax(0, 11rem). Labels wider than 11rem overflowed into the value column.
Fix: change label column sizing to max-content so it grows to fit the widest label. Short labels in other instances of the same class (This build env block, etc) keep their compact rendering since max-content only grows as needed.
Single CSS line change. One fix covers both surfaces.
Verified locally with npm run dev — labels and address values now sit on separate columns cleanly with no overlap.
mentioned in issue #214
mentioned in commit
d8afd4f1bfmentioned in merge request !392