Logout Button Does Not Show Hover State Unlike Delete Button

Open Beginner friendly

#1,961 opened on Jul 31, 2026 0 comments 0 reactions 0 assignees View on GitHub

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: javascript
Domain: frontend

Research direction

Start the Enatega Web app and navigate to Profile → Settings to reproduce the difference between the Delete and Logout buttons. Locate the corresponding Profile/Settings UI components by searching for their labels, compare their interaction styling, and verify that Logout shows a consistent hover state when the behavior is fixed.

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: JavaScript
Stars: 0
Forks: 1
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.