Margaret-Petersen / Margaret-Petersen/python-based-food-ordering-system
"Not Verified" Button Looks Disabled in Profile Settings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
In the Profile → Settings section, the "Not Verified" button for the mobile number looks like a disabled element due to its faded red styling. This creates confusion for users as it is unclear whether the button is clickable or just an indicator.
To Reproduce
Steps to reproduce the behavior:
Log in to Enatega Web.
Go to Profile → Settings.
Check the mobile number verification status.
Notice that the "Not Verified" button looks like a disabled state.
Expected behavior
The "Not Verified" element should either:
Look clearly clickable (styled like an actionable button to start verification), OR
Be replaced with a clear label if it is only meant to indicate status.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
Labels: Enatega Website, 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 by reproducing the issue in Enatega Web under Profile → Settings and locate the mobile-number verification status component. Check how the “Not Verified” element is styled and determine whether it is intended to start verification or only show status. Done means its appearance and behavior clearly communicate that purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100