This seems to be fixed in 1.8.0.

Although I don't know what your PR then maybe changed @giemic8?

@freelon Are you sure? I can reproduce this Bug on 1.8.0

I will check again tomorrow on my work machine, where it worked last time with 1.8.0, but didn't with 1.7.1.

Interestingly I just tried it out on my personal laptop (which runs the same OS) and I don't have the issue there even in 1.7.1. Could it have something to do with the collection involved, the kind of changes, or some dependency of the app that was updated in the meantime (bruno has 6 packages it depends on on Arch)?

Possible duplicate of #1396

I just checked it again on my work machine (bruno 1.8.0) - it works @giemic8

I have to correct myself - now I do stumble upon the problem again in another request.

One thing I was able to figure out what the difference might be: it works if requests without a BODY were changed. As soon as the request has a body (even if the change is in the URL), it's broken.

@freelon The issue only exist if you have a json in the body. Maybe this hint will help you.

Changing the state of the unsaved item back to the original saved state triggers the issue consistently for me.

Steps to repro:

• Change the method of a request to a different method
• the floppy icon becomes orange
• change the method back to the original method
• the floppy icon stays orange
• click the floppy button
• the save message is displayed
• the floppy icon stays orange
• try to close the request tab
• an unsaved changes message is displayed

Hi, I'm using Bruno 1.19.0, but I still get the same issue.
When I try to close an unsaved request, I click on save and it does nothing -- neither it saves, nor it closes the popup.