Margaret-Petersen / Margaret-Petersen/python-based-food-ordering-system
Change Cursor to Pointer (Hand) for Clickable Cards/Elements
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Yes. Currently, some clickable cards or elements in the interface do not visually indicate that they are interactive. The default arrow cursor remains the same, which can confuse users and reduce discoverability of actions.
Describe the solution you'd like
The cursor should automatically change to a pointer (hand cursor) when hovering over any card or UI element that is clickable. This provides a clear visual cue that the element is interactive.
Describe alternatives you've considered
Adding hover animations or visual shadows (which could supplement but not replace the cursor change)
Adding a tooltip or label to hint that it’s clickable (less intuitive than a cursor change)
Additional context
This small UI/UX improvement can significantly enhance usability, especially for new users who may not intuitively know which elements are actionable. It also brings consistency with common web behavior standards.
Recording.2025-06-17.102824.mp4
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.
Research direction
Start by locating the interface components that render clickable cards and other interactive elements, then identify which ones currently lack a pointer cursor. Verify the affected elements in the running interface by hovering over them and confirm that every clickable card or element shows the pointer cursor without changing non-interactive elements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100