MMBUGS-961 - [Mobile][Wallet][8.15.1] Screen Display Issue - Polygon address copy button is behind the phone’s navigation Bar.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, react-native, typescript
- Domain
- mobile
Research direction
The payload names no file, so begin on the Receive screen and the scrollable network list where Polygon appears, then check how the bottom edge is padded or inset on Android. The likely cause is content sitting under the system navigation bar, but confirm that in the code before changing it. Done means the Polygon copy row can be scrolled fully above the navigation bar on an Android device, and iOS behaviour stays the same.
Written by the indexing model from the issue text.
Description
MMBUGS-961 - [Mobile][Wallet][8.15.1] Screen Display Issue - Polygon address copy button is behind the phone’s navigation Bar.
See the video recording; it’s close to the end. They’re using an Android device.
User taps on Receive, then scrolls down the list and cannot choose Polygon because it’s displayed behind the phone’s navigation bar.
I cannot reproduce on IOS.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 1.7k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 635
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/metamask-mobile
-
[Bug]: Dapp Connectivity - Network list unordered mixing testnets with mainnetsPossibly taken @DostoevskysPiano claimed this 13 days ago. OpenINVALID-ISSUE-TEMPLATE regression-prod-8.17.0 Sev3-low ta-bot-triage team-mobile-ux type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/metamask-mobile#38123 ·
Maintainers usually reply within 1 day
-
client-controller-update ta-bot-triage team-swaps-and-bridge
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/metamask-mobile#37841 ·
Maintainers usually reply within 1 day
-
client-controller-update ta-bot-triage team-core-platform
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#37042 ·
Maintainers usually reply within 1 day
-
client-controller-update ta-bot-triage team-confirmations
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36997 ·
Maintainers usually reply within 1 day
-
client-controller-update ta-bot-triage team-earn
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36940 ·
Maintainers usually reply within 1 day
All issues in MetaMask/metamask-mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
zapcooking/frontend#946 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WiliamRosa/cosmos-semantic-platform#40 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
liberation-data/drivine#733 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
makecindy/cindy#10062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day