Fix/shortcut hover flicker

[ramlal-01]

🚀 Fix: Shortcuts Panel Hover Flickering

🐛 Issue

The "Shortcuts" panel was behaving inconsistently on hover:

• Initially opens as a narrow vertical panel
• Expands into a rectangle when cursor moves slightly outside
• Shrinks back when hovered again
• Causes continuous flickering/juggling effect, especially around the "Got it" button

🎯 Expected Behavior

The panel should remain stable in size and layout once opened, without unexpected transitions based on cursor movement.

⚠️ Root Cause

The layout was being controlled by hover-based styling, where the hover area dynamically changed (width/position).
This caused repeated mouseenter / mouseleave triggers, leading to flickering.

✅ Fix Implemented

• Stabilized the panel layout to prevent dynamic resizing on hover
• Removed dependency on unstable hover-based width/position changes
• Ensured consistent rendering regardless of minor cursor movement
• Improved interaction around inner elements (e.g., "Got it" button)

🧪 Testing

• Verified panel remains stable during hover interactions
• Tested cursor movement inside and outside panel boundaries
• Confirmed no flickering or layout shifts

🔗 Related Issue

Fixes #917

---

📌 Result

The shortcuts panel now behaves consistently and provides a smooth user experience without flickering.

[vercel]

@ramlal-01 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[ramlal-01]

I have solved the issue.
Please look towards it and tell me if any error exists. @Priyanshu-byte-coder

[Priyanshu-byte-coder]

Thanks for the fix! A couple of things to address before merge:

1. ** deleted** — This PR removes all 55 lines from . That file documents required environment variables for contributors setting up the project locally. Please restore it.

2. Conflict with #923 — PR #923 fixes the same hover-flicker issue with similar changes to and . Please rebase on latest main and resolve any conflicts.

3. ** churn** — The lockfile shows unrelated dependency changes. Please restore it by running
   up to date, audited 542 packages in 5s

176 packages are looking for funding
run npm fund for details

16 vulnerabilities (7 moderate, 9 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details. on a clean checkout of latest main before pushing.

[Priyanshu-byte-coder]

Thanks for the fix! A couple of things to address before merge:

1. .env.example deleted — This PR removes all 55 lines from .env.example. That file documents required environment variables for contributors. Please restore it.

2. Conflict with #923 — PR #923 fixes the same hover-flicker issue with overlapping changes to KeyboardShortcuts.tsx and ShortcutsModal.tsx. Please rebase on latest main and resolve conflicts.

3. package-lock.json churn — Lockfile shows unrelated dependency changes. Please regenerate it from a clean checkout of latest main.

[ramlal-01]

Thanks for the review!

• Restored .env.example
• Rebased on latest main and resolved conflicts
• Regenerated clean package-lock.json

Please review again @Priyanshu-byte-coder