Logout Button Does Not Show Hover State Unlike Delete Button
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the Profile → Settings section of Enatega Web and reproduce the difference between the Delete and Logout buttons by hovering over each. Trace the Logout button's styling and compare it with the Delete button's hover behavior. Done means the Logout button provides a clear hover state consistent with the Delete button or another established visual effect.
Written by the indexing model from the issue text.
Description
Describe the bug
In the Profile → Settings section, when hovering over the Delete button, it gets highlighted to indicate that it is clickable. However, the Logout button does not provide any hover feedback, making it look more like static text rather than an actionable button.
To Reproduce
Steps to reproduce the behavior:
Log in to Enatega Web.
Go to Profile → Settings.
Hover over the Delete button → It highlights.
Hover over the Logout button → No hover effect is shown.
Expected behavior
The Logout button should have a similar hover state to Delete (or another consistent visual effect) to make it clear that it is clickable.
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
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from lambertf917/open-source-document-solution-system
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in lambertf917/open-source-document-solution-system
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100