mirror of
https://github.com/ProxymanApp/proxyman-windows-linux.git
synced 2026-04-27 00:45:55 +03:00
[GH-ISSUE #529] Allow setting "Body" as the default tab in the Response view #526
Labels
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxyman-windows-linux#526
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aa1134665908 on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/529
Originally assigned to: @kics223w1 on GitHub.
Hi Proxyman Team,
First of all, thanks for this great tool!
I have a question about the UI in the Response view. Currently, when I select a request, the Header tab is the one selected by default.
In my daily workflow, I'm almost always interested in the Body of the response first. This means I have to perform an extra click to switch from the "Header" tab to the "Body" tab for nearly every request I inspect.
Would it be possible to either:
Set the Body tab as the default view?
Or, allow users to customize the order of the tabs (Header, Body, Raw) so we can make "Body" the first one?
This would be a small but very helpful quality-of-life improvement that would save a lot of clicks.
Thanks for your consideration!
@kics223w1 commented on GitHub (Aug 10, 2025):
Hi @aa1134665908, I’ll discuss this feature with @NghiaTranUIT and get back to you 👍.
Basically, the Body tab always remains selected, it only switches back to the Header tab if you click on a request that does not yet have a response.
@aa1134665908 commented on GitHub (Aug 10, 2025):
Hi, thanks for the quick reply and for looking into this!
I understand the current behavior you described – that the Body tab selection is "sticky". However, the issue I'm encountering is related to my specific workflow.
I often switch back and forth between inspecting completed requests (with a response body) and checking on requests that are still pending or do not have a response. When I click on a request without a response, the view correctly switches to the "Header" tab. The problem is that when I then click back to a request that does have a response, the view remains on the "Header" tab, forcing me to manually switch to "Body" again. This frequent context switching resets the "sticky" selection.
This is why the ability to set a "hard default" tab would be so valuable. If I could configure "Body" as the primary default, it would always select it first for any request that has a response body, regardless of what I previously clicked.
Hope this clarifies my use case. Thanks again for your consideration!
@kics223w1 commented on GitHub (Aug 10, 2025):
Sure I understand. Thanks for clarifying your use case.
@kics223w1 commented on GitHub (Aug 11, 2025):
Hi @aa1134665908, I just checked with the author, and he prefers to keep everything as it is. Therefore, we won’t be implementing the feature to set a hard default tab. Thank you for your request, and have a great day 👍🏻
@Calvin-Broadhurst commented on GitHub (Aug 21, 2025):
I'd also vote for this as a future enhancement... my workflow is similar to @aa1134665908 so I encounter the same problem of having to keep re-selecting the body tab.
@kics223w1 commented on GitHub (Aug 22, 2025):
@Calvin-Broadhurst @aa1134665908 I'm working on this feature 👍🏻