"Add Address" Button Hiding "Delete" Button in List at customer app.

Open

#1,821 opened on Jul 25, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: frontend, mobile-dev

Research direction

Start by reproducing the issue in the customer app's address list and inspect the screen where the "Add Address" and "Delete" buttons are rendered. Adjust the layout so both controls remain visible and accessible, then verify that an address can be deleted without the buttons overlapping.

Written by the indexing model from the issue text.

Description

Issue: "Add Address" Button Hiding "Delete" Button in List
Description:
There is an issue at application where the "Add Address" button is obscuring or hiding the "Delete" button within a list or a user interface element.

Impact:
User Confusion: Users may face confusion while trying to delete an address from the list because the "Delete" button is not accessible or visible.

Reduced Functionality: The inability to delete addresses can affect the user's ability to manage their address book or information effectively.

Steps to Reproduce:

Access the list or section containing user addresses.
Attempt to delete an address entry.
Observe that the "Add Address" button is either overlaying the "Delete" button or causing it to be hidden from view.
Expected Resolution:
The "Add Address" button and the "Delete" button should not overlap or hide each other in the list. The user interface should be designed or adjusted to ensure that both buttons are easily accessible and functional, allowing users to manage their addresses without confusion or hindrance.
mage 2023-10-11 at 16 05 05_1fe4da65

Activity

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open 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.