gray-mueller / gray-mueller/food-ordering-app-using-python

"Not Verified" Button Looks Disabled in Profile Settings

Open
#2,580 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
4
Forks
3
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

Open the contributing guide

Research direction

Start in Enatega Web at Profile → Settings and inspect the mobile-number verification control, including whether “Not Verified” is intended to be actionable or only a status indicator. Done means the element’s visual treatment clearly communicates its role and no longer appears misleadingly disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.