You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the close window shortcut (likely Ctrl+W/Command+W) closes the entire HTTP Toolkit application instead of just the active "Send Request" tab. This behavior is inconsistent with standard practices in browsers and editors, where this shortcut typically closes only the current tab while keeping the application running.
Proposed Solution
Add a configurable option that allows users to either:
Disable the close window shortcut completely, or
Modify its behavior to close only the current "Send Request" tab instead of the entire application
Use Case
When working with multiple request tabs simultaneously, accidentally pressing the close shortcut results in losing the entire workspace rather than just closing the current tab, causing workflow disruption and potential data loss.
Expected Behavior
When the option is enabled: The close window shortcut (Ctrl+W) should only close the current active tab
Add this option to the application settings with appropriate documentation
Additional Context
This aligns HTTP Toolkit's behavior with standard patterns in browsers (Chrome, Firefox) and editors (VS Code, etc.) where Ctrl+W closes the current tab, and a different shortcut (typically Alt+F4) closes the application.
Sure, that makes sense. Looking at VS Code on Mac, it seems it uses Ctrl/Cmd+Shift+W to close a window, with Ctrl/Cmd+W closing a single tab. That seems reasonable.
Description
Currently, the close window shortcut (likely Ctrl+W/Command+W) closes the entire HTTP Toolkit application instead of just the active "Send Request" tab. This behavior is inconsistent with standard practices in browsers and editors, where this shortcut typically closes only the current tab while keeping the application running.
Proposed Solution
Add a configurable option that allows users to either:
Use Case
When working with multiple request tabs simultaneously, accidentally pressing the close shortcut results in losing the entire workspace rather than just closing the current tab, causing workflow disruption and potential data loss.
Expected Behavior
Additional Context
This aligns HTTP Toolkit's behavior with standard patterns in browsers (Chrome, Firefox) and editors (VS Code, etc.) where Ctrl+W closes the current tab, and a different shortcut (typically Alt+F4) closes the application.
Does this affect you too? Click below and add a 👍 to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.
The text was updated successfully, but these errors were encountered: