lambertf917 / lambertf917/multi-delivery-solution
Enatega Customer Application: Place Order Button Not Visible and Improperly Positioned on Checkout Screen
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On the checkout screen, the "Place Order" button is not clearly visible to the user. It is incorrectly stuck at the bottom edge of the screen, blending into the background or UI, making it difficult to recognize as an actionable button. This poor visibility and placement results in a confusing user experience, as the user may not realize how to complete the order.
Steps to Reproduce:
Navigate to the checkout screen after adding items to the cart.
Observe the bottom of the screen.
Notice that the "Place Order" button is either:
Not clearly visible,
Partially hidden by screen margins or navigation elements,
Not styled distinctly as a button.
Expected behavior
The "Place Order" button should be prominently displayed with clear visibility, appropriate padding, and proper placement above the screen edge or navigation bar.
Smartphone (please complete the following information):
Device: [e.g. Samsung A15]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. Latest]
Labels: Enatega Multivendor Customer App, High Priority, Bug
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 at the customer application's checkout screen and reproduce the issue after adding items to the cart, focusing on the Place Order button at the bottom edge. Check its visibility, padding, and position relative to screen margins or navigation elements; done means the button is clearly styled, fully visible, and placed above the screen edge or navigation bar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100