Skip to content

Spaces in a query parameter are not taken into account #8091

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
Closed
1 task done
amanfromfrance opened this issue Oct 17, 2024 · 10 comments · Fixed by #8627
Closed
1 task done

Spaces in a query parameter are not taken into account #8091

amanfromfrance opened this issue Oct 17, 2024 · 10 comments · Fixed by #8627
Assignees
@yaoweiprc
Labels
B-bug Bug: general classification S-verified Status: Verified by maintainer

Comments

@amanfromfrance
Copy link

Expected Behavior

When typing a string that contains spaces as the value of a query parameter, it is expected that the string is exactly what has been typed in.

For example, if the query parameter is used to pass a geographical address to the API method and I type the following address:

Rue de la Rigourdière, 35510 Cesson-Sévigné

Then it is expected that the value of the query parameter is this address:

image

Actual Behavior

However it is not the current behaviour: spaces are not taken into account and the query parameter value looks like the print screen below after typing all the characters on the keyboard:

image

One has to either go back/up into the string using the mouse pointer and/or using the backspace key multiple times in order to make Insomnia accept one single space. Which is pretty annoying.

This behaviour appeared recently but could be observed at least in the previous release.

Reproduction Steps

  1. Add a query parameter
  2. Type a string that contains spaces
  3. Confirm that all spaces are missing from the string

Is there an existing issue for this?

Additional Information

Insomnia Help information:

  • Version: Insomnia 10.1.0
  • Build date: 16/10/2024
  • OS: Windows_NT x64 10.0.19045
  • Electron: 31.4.0
  • Node: 20.16.0
  • Node ABI: 125
  • V8: 12.6.228.30-electron.0
  • Architecture: x64

Windows System information:

  • Edition: Windows 10 Entreprise
  • Version: 22H2
  • Installed: ‎05/‎05/‎2022
  • Build: 19045.4894
  • Windows Feature Experience Pack 1000.19060.1000.0

Insomnia Version

10.1.0

What operating system are you using?

Windows

Operating System Version

Windows_NT x64 10.0.19045

Installation method

Download from insomnia.rest

Last Known Working Insomnia version

No response
@amanfromfrance amanfromfrance added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Oct 17, 2024
@Shahriar-Sazid
Copy link

I'm facing the same issue after update. This is a serious bug which is hampering much. Please fix the issue.

@brunogabriel
Copy link

Here same, OS: Manjaro Linux x86_64, GNOME 47.2.
Insomnia version: 10.2.0

@FlorianEagox
Copy link

Still here on arch / Endevouros with KDE Plasma

@notjaywu
Copy link
Contributor

It seems related to #7739

@notjaywu notjaywu added S-verified Status: Verified by maintainer and removed S-unverified Status: Unverified by maintainer labels Dec 25, 2024
@camacici
Copy link

camacici commented Apr 2, 2025

Same behaviour for body>Multipart

Image

Every time I need a "space" I have to copy and paste it from another place 🤦

How could it be possible that a problem like this remain open for over a 6 months!?

@jmyoung
Copy link

jmyoung commented Apr 15, 2025

Version 11.0.2, Windows x64, also happening to me. This is incredibly frustrating, spaces just get eaten. I can sometimes make it allow me to enter a space by clicking on the UI elements first, but entering in any query parameters that include spaces is very annoying.

@amanfromfrance
Copy link
Author

I'm glad I'm not the only one having this issue... and at the same time it's also sad to see that more than 6 months later it hasn't been solved.

But at least it's been acknowledged as now the status is set to verified, that's a good start!

@notjaywu
Copy link
Contributor

Thanks for the reporting. We are looking into this issue. For now, you can use Bulk Edit as a workaround.

Image Image

@camacici
Copy link

camacici commented Apr 17, 2025 •
edited
Loading

Thanks @notjaywu

In Body > Form Data/Multipart there isn't the "Bulk edit" functionality.
I've checked the version, it's 11.0.2, the lastest.

Image

@yaoweiprc yaoweiprc mentioned this issue Apr 17, 2025
Closed
@yaoweiprc
Copy link
Contributor

This issue stems from a bug in react-aria. I've submitted an issue to them, and I'm looking for a workaround to solve it.
adobe/react-spectrum#8104

This was referenced Apr 18, 2025
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yaoweiprc yaoweiprc

Labels
B-bug Bug: general classification S-verified Status: Verified by maintainer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

A workaround for the space issue in key-value editor [INS-5274] Kong/insomnia
8 participants
@camacici @FlorianEagox @yaoweiprc @brunogabriel @jmyoung @Shahriar-Sazid @amanfromfrance @notjaywu