fix(frontend): keep token pickers inside visual viewport (#632) #1144
No reviewers
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!1144
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/632-keplr-token-picker"
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
visualViewportplus DEX tab bar, IME occlusion, optional in-app chrome, and a 44px finger gap so last options no longer sit on Keplr’s URL bar.docs/frontend.mdandskills/AGENTS_FRONTEND_PORTAL_LISTBOX_VIEWPORT.md. Verify:make verify-issue-632.Test plan
make verify-issue-632(unit + docs; retested)detectWalletInAppBrowsere2e-smoke(5 workers):#498CLS,#632pay/receive clearance + last-option click, Trade pair CLS + phone clearanceCloses #632
Closes #632
marked this merge request as ready
added 18 commits
maine3e18e89- merge origin/main into fix/632-keplr-token-pickerCompare with previous version
mentioned in commit
6af8261cfdmentioned in issue #629
mentioned in issue #632
mentioned in issue #638
mentioned in issue #630
mentioned in issue #631
mentioned in issue #627
mentioned in issue #526