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.

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 ( optimzation ) : Testbench driver location #420

Open
1 task done
ThatDeparted2061 opened this issue Jan 22, 2025 · 2 comments · May be fixed by #432
Open
1 task done

🐞 Bug ( optimzation ) : Testbench driver location #420

ThatDeparted2061 opened this issue Jan 22, 2025 · 2 comments · May be fixed by #432
Labels
🐞 bug Something isn't working pending triage issue yet to be reviewed by maintainers

Comments

@ThatDeparted2061
Copy link

Is there an existing issue for this?

  • I have searched the existing issues.

Describe the bug

The location of the testbench driver shouldn't be over other menu options move it below the menu or place it somewhere better.

Steps to Reproduce

Open the simulator it'll be visible

Expected Behavior

Shouldn't be hovering over other menu options.

Screenshots

Image

Is the faced issue/bug related to the Vue simulator?

Yes

Used Vue simulator with or without backend?

Without Backend

Is the bug present only on the dev server, the build, or both?

Both

Device Information

Ubuntu 24.04 LTS
Chrome 132.0.6834.83

Additional Context

No response

Are you working on this issue?

No

@ThatDeparted2061 ThatDeparted2061 added pending triage issue yet to be reviewed by maintainers 🐞 bug Something isn't working labels Jan 22, 2025
@maheshcodes12
Copy link

Can I work on this issue?

@ThatDeparted2061
Copy link
Author

Yes you can, In your PR do give a reason for your choice for positioning if the option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working pending triage issue yet to be reviewed by maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants