Skip to content

Desktop client scroll issues #1719

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.

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

Closed
voidmain opened this issue Feb 13, 2016 · 14 comments
Closed

Desktop client scroll issues #1719

voidmain opened this issue Feb 13, 2016 · 14 comments

Comments

@voidmain
Copy link

I'm using the desktop (Mac) version of Postman and the scrolling makes it almost too painful to use the app. The response textarea is always 50 lines of text and this isn't configurable. After I submit a request, I can only see 20 or less lines of the response. I have to move my cursor to the side of the app, outside of the request body textarea and then scroll the tab down until the full response textarea is visible.

I have to repeat this process in the opposite direction to change the request and then again to view the response. Plus, the width of the area that I can do this tricky little scroll in is about 20 pixels. That makes it really challenging to do this maneuver over and over.

This is a usability killer.

i've attached screen shots as illustrations.

Viewing and editing request body

Viewing the response body

@glennschmidt
Copy link

I thought I must be the only one having this problem. It's been driving me nuts since early versions of Postman.
I'm also using the Mac desktop version, maybe it is specific to that version.

@cruisencode
Copy link

I'm having the same issue as well.

@aditikul
Copy link

aditikul commented Aug 1, 2016

@voidmain @glennschmidt @cruisencode Totally understand the issue. We are looking into this however we are using a plugin for the response view which limits what we can do to solve this. For now I would recommend using the shortcut Cmd+Up/Cmd+Down to quickly jump scroll. In the meantime we will work on solving this on a longer term ETA.

@a85
Copy link
Contributor

a85 commented Aug 4, 2016

@aditikul The Cmd+Up/Cmd+Down shortcuts do not work after a click in the sidebar area. Can you check this once?

@ahmetgeymen
Copy link

I think request settings page below the tab should not be scrollable area. Instead the textview that contains the response body is scrollable by default though. The end of the response body textview remains below the window area. You have to scroll down to see the end of it which is painful to figure out how to do.

@a85
Copy link
Contributor

a85 commented Apr 8, 2017

Postman now has a two pane view: View > Toggle Two-pane view. The request and response can appear side by side.

@a85 a85 closed this as completed Apr 8, 2017
@mfoote
Copy link

mfoote commented Mar 17, 2018

i am not seeing... View > Toggle Two-pane view

@Alton-Powell
Copy link

Click on Settings and then on the General tab you will find "Two Pane View". Turn it on.

@raketenolli
Copy link

Equally dysfunctional. I cannot scroll inside the response body using my mouse wheel (Windows 10, desktop app).

@ahmetgeymen
Copy link

After two pane feature is brought, I began to use request view and response view side by side. Seems more effective.

@mdickin
Copy link

mdickin commented Jan 10, 2019

I don't know why this is closed, I still frequently have issues using the scroll wheel inside the response. It seems there's some distinction between scrolling while the cursor is over the left half of the text area versus the right. But then sometimes it doesn't work over the left either.

I'm using Windows desktop v6.6.1

@yarick
Copy link

yarick commented Jan 15, 2019

I am seeing this issue on OSX as well

@brcinho
Copy link

brcinho commented Mar 19, 2019

I experience the same problem in version 7 on Windows desktop client but only on external monitor, not on my main monitor. In general the scroll stops working in any Postman user control so I have to use scrollbars directly with mouse on external monitor.

My main monitor has scaling to 200%, while external one doesn't have scaling, although I don't know if it is anyhow related to the issue, just trying to give as much inputs...
Os is Windows 10 (1809)

@cstephen98
Copy link

So how many years to people have to complain about this issue before they fix it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests