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

URL lock occurs after WebSocket connection and cannot be unlocked until switching requests #8265

Open
1 task done
rodkevich opened this issue Dec 23, 2024 · 3 comments · May be fixed by #8269
Open
1 task done

URL lock occurs after WebSocket connection and cannot be unlocked until switching requests #8265

rodkevich opened this issue Dec 23, 2024 · 3 comments · May be fixed by #8269
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer

Comments

@rodkevich
Copy link

rodkevich commented Dec 23, 2024 •
edited
Loading

Expected Behavior

Given I have a WebSocket request in Insomnia
When I connect to the WebSocket server
Then the URL input field should be locked and not editable
And the URL input field should remain locked
But the URL input field should unlock when the WebSocket connection is closed without switching to another request
And I should be able to change the parameters in the URL input field after unlocking

Actual Behavior

the URL input field remains locked until I switch to a different request

Is there an existing issue for this?

Which sync method do you use?

  • Local only

Insomnia Version

Version: Insomnia 10.3.0

What operating system are you using?

macOS

Operating System Version

15.1.1 (24B91)

Installation method

download

Last Known Working Insomnia version

idk (made a request in discussions for help)
@rodkevich rodkevich added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Dec 23, 2024
@notjaywu
Copy link
Contributor

I can’t reproduce this issue with v10.3.0 on my end. Can you share more information? Is it a local WebSockets server?

Verified the following cases:

  1. Disconnect worked, and the field was unlocked correctly.
  2. The WebSockets server closed the connection and it unlocked as expected.

@rodkevich
Copy link
Author

rodkevich commented Dec 24, 2024 •
edited
Loading

I can’t reproduce this issue with v10.3.0 on my end. Can you share more information? Is it a local WebSockets server?

Verified the following cases:

1. `Disconnect` worked, and the field was unlocked correctly.

2. The WebSockets server closed the connection and it unlocked as expected.

@notjaywu hello
thanks for responding
I forgot to show that after switching to another and back everything will work as expected
but it will, if anything

Screen.Recording.2024-12-24.at.1.25.03.PM.mov

@notjaywu
Copy link
Contributor

notjaywu commented Dec 24, 2024 •
edited
Loading

Thanks for your information. We are looking into it.

@CurryYangxx CurryYangxx linked a pull request Dec 25, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: editor did not unlock after websocket disconnect Kong/insomnia
2 participants
@rodkevich @notjaywu