bug: Incorrect cursor type (text selector instead of pointer) on feature tags/buttons

[Vaanshimadaan]

When hovering or scrolling over the white informational buttons/tags located at the bottom left of the landing page (e.g., "19 visualizers", "Runs in browser", "Open source", "Free to use"), the mouse cursor changes to a text insertion/typer cursor (cursor: text) instead of a clickable pointer cursor (cursor: pointer).

This creates a confusing user experience as these elements look like actionable tags or buttons but behave visually like plain unclickable text.

o Reproduce
Steps to reproduce the behavior:

Go to the landing page.

Scroll down to the section under the main CTA buttons ("Explore visualizers").

Hover the mouse cursor over any of the white outline buttons/tags (e.g., "19 visualizers").

Expected behavior
The cursor should change to a pointer (hand icon) to indicate that these are interactive tags/buttons, or remain a default arrow if they are completely static elements, but it should definitely not change to a text/typer cursor

Observe that the cursor changes to a text selector.

[Vaanshimadaan]

I would like to work on this issue under GSSoC'26 please assign this to me

[mayank188]

Hi @Vaanshimadaan

I would like to work on this issue under GSSoC'26.

I have reviewed the bug description and understand that the issue is caused by an incorrect cursor style on the feature tags/buttons. I can fix the cursor behavior by ensuring the appropriate cursor: pointer (or default if the elements are non-interactive) is applied consistently while preserving the existing UI and accessibility.

Kindly assign this issue to me. I will submit a clean PR following the project's contribution guidelines.

Thank you!

[28106]

Hi @Vaanshimadaan, I’d like to work on this issue.

I’ll investigate the feature tags/buttons on the landing page and fix the incorrect cursor behavior so they reflect the intended interaction state properly. If these elements are meant to be clickable, I’ll update them to use cursor: pointer; if they’re purely informational/static, I’ll make sure they use an appropriate non-text cursor instead of the current text-selection cursor. Along with the direct fix, I’ll also review the related styling for these tags/buttons to ensure consistent hover behavior and cursor states across similar landing page elements.

Once assigned, I’ll test the fix across the affected feature tags like “19 visualizers”, “Runs in browser”, “Open source”, and “Free to use” to make sure the UX is clear and consistent on different screen sizes as well.

[aaniya22]

pls assign this to me under gssoc