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

An open side panel should not block running another plugin #130

Open
heeckhau opened this issue Jan 16, 2025 · 1 comment · May be fixed by #153
Open

An open side panel should not block running another plugin #130

heeckhau opened this issue Jan 16, 2025 · 1 comment · May be fixed by #153
Assignees
@Codetrauma

Comments

@heeckhau
Copy link
Member

If the side panel is already open and the user wants to run another plugin, the side panel should not block that plugin, but should autoclose and the side panel for the other plugin should open.
@heeckhau
Copy link
Member Author

heeckhau commented Feb 5, 2025

Use refresh as a quickfix?

We may also consider adding a tab for the new process

@Codetrauma Codetrauma linked a pull request Feb 27, 2025 that will close this issue
Sidepanel refreshes on subsequent plugin runs if still open #153
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Codetrauma Codetrauma

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Sidepanel refreshes on subsequent plugin runs if still open tlsnotary/tlsn-extension
2 participants
@heeckhau @Codetrauma