-
Notifications
You must be signed in to change notification settings - Fork 109
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.
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
Bug (UI): When ElementsPanel is moved to overlap the Navbar, it becomes locked there and loses the ability to be dragged. #260
Comments
@Arnabdaz please take a look at this. I have already started working on this. please assign this to me. Also please let me know if you want any changes in the issue |
@Chandrachur67 you can work on the issue check now the tabsbar must also be having the same issue after merging #223 fix that also ... mostly its a issue of z-index. |
@Arnabdaz thank you so much. I will surely consider the changes in #223 . I need some clarifications regarding the solution Which solution you want me to implement
clarifications needed regarding approach 1: clarifications needed regarding approach 2: Thanks again. |
We would go with 1 Check the old simulator at circuitverse.org/simulator implement as it is in there. Also when the tabsbar expand make sure the tabsbar is above the panels. |
Thanks for the clarification. The solution is almost ready. I will raise a pr very soon. |
hi , i want to work on this issue , as there is an inactivity on this issue from various months ,so kindly assign me @Arnabdaz |
Describe the bug
The draggable ElementsPanel can be moved to overlap with the Navbar component and if we leave that there then we lose the functionality to move the ElementsPanel further because the Navbar appears on top of the ElementsPanel Component.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I can think of two possible solutions.
Screenshots
This is movable
This is not movable
Device Information [optional]:
Additional context
I think need to think of one more edge case i.e. when Navbar options are expanded. Considering this case the first possible solution seems better to me.
Are you working on this issue? (Yes/No)
Yes
The text was updated successfully, but these errors were encountered: