BUG:Missing Tooltip for nav icons in dashboard
@MuKuL-DiXiT is already working on this.
Since Dec 8, 2025.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the dashboard view and inspect the left navbar and right logout icon, especially the Link elements mentioned in the issue. Add visible hover labels matching each icon's action and verify the result in both light and dark modes; done means every navbar icon displays its label on hover.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
📌 Issue Overview
🔍 Steps to Reproduce
- Open the dashboard view.
- Hover over any of the navbar icons on the left or the logout icon on the right.
- Notice that no tooltip or label appears.
- Users must guess based on icon shape alone.
🎯 Expected Behavior
When hovering over any icon in the navbar:
A tooltip should appear showing the label (e.g., “Dashboard”, “Users”, “Logout”).
Tooltip should be consistent across light/dark modes.
Tooltip improves navigational clarity and reduces guesswork.
🚨 Actual Behavior
No tooltip appears on hover for any icon.
Icons rely entirely on visual recognition, which is not always obvious.
Although sr-only labels exist, they are only accessible to screen readers and not visible to sighted users.
📷 Screenshot
current:
expected:
💡 Suggested Improvements
I've fixed it on my end by adding the title for Link element
Record
- I agree to follow this project's Code of Conduct
- I want to work on this issue
- Dominant language
- TypeScript
- Stars
- 101
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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.
More from AOSSIE-Org/InPactAI
-
UI Bug: Low contrast makes input text unreadable in Sign Up and Login formPossibly taken @Abhik-Mudi claimed this 310 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AOSSIE-Org/InPactAI#218 ·
-
DOCS UPDATE: Fix incorrect .env file location in Backend Setup instructionsPossibly taken @PulkitDadwal claimed this 325 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
AOSSIE-Org/InPactAI#201 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
AOSSIE-Org/InPactAI#314 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
AOSSIE-Org/InPactAI#312 ·
-
FEATURE REQUEST: Add API Pagination to Backend List EndpointsMay be free again @alphacoder-hash claimed this 196 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
AOSSIE-Org/InPactAI#307 · 2 comments ·
All issues in AOSSIE-Org/InPactAI
Similar issues
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
agent-task risk:low
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
guyellis/http-status-check#512 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/playwright#43327 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/TypeScript#64758 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opensearch-project/OpenSearch-Dashboards#12937 ·
Maintainers usually reply within 2 days