You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dropdown menu in the Netlify deployment (https://circuitverse.netlify.app/simulatorvue) is getting clipped behind the navigation bar, making the menu options inaccessible. However, in the original CircuitVerse website (https://circuitverse.org/simulator), the dropdown appears correctly. This is a critical UI issue as users will not be able to see or interact with the dropdown menu properly.
Additionally, the underline appears in a different position between the hover and non-hover states, causing an inconsistent and visually unappealing effect. The dropdown arrow animation also exhibits abnormal behavior, which impacts the overall user experience.
I've already come up with these two design which i believe fits the overall UI of the page.
tis there is some other suggestion or any modification, let me know so that I can implement that and raise a PR.
Is there an existing issue for this?
Describe the bug
The dropdown menu in the Netlify deployment (https://circuitverse.netlify.app/simulatorvue) is getting clipped behind the navigation bar, making the menu options inaccessible. However, in the original CircuitVerse website (https://circuitverse.org/simulator), the dropdown appears correctly. This is a critical UI issue as users will not be able to see or interact with the dropdown menu properly.
Additionally, the underline appears in a different position between the hover and non-hover states, causing an inconsistent and visually unappealing effect. The dropdown arrow animation also exhibits abnormal behavior, which impacts the overall user experience.
Steps to Reproduce
Expected Behavior
Screenshots
CircuitVerse_Navbar_issue.mp4
In the original site:

In the vue v0 version:

Is the faced issue/bug related to the Vue simulator?
Yes
Used Vue simulator with or without backend?
None
Is the bug present only on the dev server, the build, or both?
Both
Device Information
Additional Context
No response
Are you working on this issue?
Yes
The text was updated successfully, but these errors were encountered: