[GH-ISSUE #1555] Response block should be expanded by default #495

New issue

Closed

opened 2026-03-16 15:40:15 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 15:40:15 +03:00

Owner

Originally created by @xairoo on GitHub (Mar 21, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1555

Originally assigned to: @liyasthomas on GitHub.

expandResponse @ response results block should be true by default because it's more intuitive.

Scrolling over the full viewport is better than scrolling in a inline scroll block.

Clicking on "expand response" again and again after every request isn't cool ;-)

Originally created by @xairoo on GitHub (Mar 21, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1555 Originally assigned to: @liyasthomas on GitHub. `expandResponse` @ response results block should be `true` by default because it's more intuitive. Scrolling over the full viewport is better than scrolling in a inline scroll block. Clicking on "expand response" again and again after every request isn't cool ;-)

kerem

2026-03-16 15:40:15 +03:00

closed this issue
added the
core

discussion
labels

kerem commented

2026-03-16 15:40:31 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 22, 2021):

@Xairoo thanks for the suggestion. We're planning on revamping the entire UI with less viewport scroll and more inline block scroll. That should resolve this issue, we're open to ideas on what all can be improved apart from scrolling. Let me know which part, components need improvements. I'm letting this issue stay untill we finalize a new UI proposal which fix some existing clutter.

@liyasthomas commented on GitHub (Mar 22, 2021): @Xairoo thanks for the suggestion. We're planning on revamping the entire UI with less viewport scroll and more inline block scroll. That should resolve this issue, we're open to ideas on what all can be improved apart from scrolling. Let me know which part, components need improvements. I'm letting this issue stay untill we finalize a new UI proposal which fix some existing clutter.

kerem commented

2026-03-16 15:40:36 +03:00

Author

Owner

@xairoo commented on GitHub (Mar 22, 2021):

Depends on how you handle this. The important part for me is the response and mainly the response body.

The Parameters, Header, ... block fits the content size, which is great.
To toggle the view of this block, we could just click again on the active tab title to hide the content (but keeps the tab titles of course).
And instead of the content like the parameters, ..., + Add new button there could be a Click to expand/toggle the view button (and clicking the tab itself will toggle the content too).

Also the state should be saved.

@xairoo commented on GitHub (Mar 22, 2021): Depends on how you handle this. The important part for me is the response and mainly the response body. The `Parameters`, `Header`, ... block fits the content size, which is great. To toggle the view of this block, we could just click again on the active tab title to hide the content (but keeps the tab titles of course). And instead of the content like the parameters, ..., `+ Add new` button there could be a `Click to expand/toggle the view` button (and clicking the tab itself will toggle the content too). Also the state should be saved.

kerem commented

2026-03-16 15:40:41 +03:00

Author

Owner

@liyasthomas commented on GitHub (Aug 30, 2021):

With the release of v2 - we made the response section to be expanded to full length by default.

@liyasthomas commented on GitHub (Aug 30, 2021): With the release of v2 - we made the response section to be expanded to full length by default.