Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature] Improve UX for "Explore CC" Dropdown (Smooth Transitions and Better Interaction) #354

Open
1 task done
Soham-Kakkar opened this issue Nov 22, 2024 · 0 comments
Open
1 task done

[Feature] Improve UX for "Explore CC" Dropdown (Smooth Transitions and Better Interaction) #354

Soham-Kakkar opened this issue Nov 22, 2024 · 0 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on

Comments

@Soham-Kakkar
Copy link

Soham-Kakkar commented Nov 22, 2024 •
edited
Loading

Problem

The "Explore CC" dropdown currently opens and closes immediately without any smooth transitions. This behavior, while functional, does not align with modern UI/UX standards. Additionally, the "Explore CC" button moves its position when toggled, which may disrupt the user's focus and create a less intuitive experience.

Current implementation:

Screen.Recording.2024-11-22.163855.mp4

Description

Enhancing the dropdown with smooth CSS transitions would make the experience feel more polished and visually pleasing. Additionally, keeping the "Explore CC" button static or improving its interaction with the dropdown could ensure a more cohesive user experience.

Additional context

This enhancement will make the interaction feel more polished and user-friendly.

Implementation

  • I would be interested in implementing this feature.
@Soham-Kakkar Soham-Kakkar added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Nov 22, 2024
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 26, 2024
@possumbilities possumbilities moved this from Triage to Backlog in possumbilities Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on
Projects
possumbilities
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Soham-Kakkar @possumbilities