marthaegrimaldi / marthaegrimaldi/meal-ordering-app-using-react-native
Enatega Customer Application: (UI-Fix) Cross (✕) Icon Button is Cut Off on Order Status Screen
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Description:
On the Order Status screen (after an order is placed), the close/cross (✕) icon button appears partially cut off, either at the top, side, or corner of the screen. This affects its visibility and usability, making it unclear to the user that it's an interactive element to dismiss or close the screen.
Expected Behavior:
The cross icon should be fully visible, properly aligned within its container, and accessible for tapping/clicking without obstruction.
Steps to Reproduce:
Place an order through the app or website.
Navigate to the Order Status screen.
Observe the position and rendering of the cross (✕) icon.
Impact:
Aesthetic/UI inconsistency
Reduced usability (hard to tap or recognize the button)
Confusing UX, especially for users wanting to exit the screen
*Possible Causes:
Missing padding/margin on the icon container
Incorrect positioning (e.g. absolute without safe area consideration)
Overlapping elements or clipped overflow
Smartphone (please complete the following information):
Device: [e.g. Infinix hot 50]
OS: [e.g. Android ]
Browser [e.g. Application]
Version [e.g. Latest]
Contributor 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.
Research direction
Start by reproducing the issue on the Order Status screen after placing an order, then locate the screen entry point and the cross icon button in the React Native application. Check how its container is positioned and clipped; done means the icon is fully visible, aligned, and tappable without obstruction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100