[GH-ISSUE #627] Request/response formatted as json is not scrollable with mouse wheel #625

New issue

Open

opened 2026-03-03 19:20:25 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 19:20:25 +03:00

Owner

Originally created by @grigorye on GitHub (Sep 21, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/627

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

2.6.0

macOS Version? (Ex. mac 10.14)

10.15.6

Steps to reproduce

Make a request that with json in the body or response
Navigate to request/response pane and select "Body/JSON" as the format
Adjust the pane height to make the scrollbar visible
Try to scroll the pane content with mouse wheel

Expected behavior

The content is scrollable with mouse wheel.

Actual behavior

The content is scrollable only by dragging the scrollbar.

Note that this problem is specific to Body/JSON case - if you select e.g. "Raw", "Header" or Body/Tree View, the content is scrollable with mouse wheel as expected.

Screenshots (optional)

Originally created by @grigorye on GitHub (Sep 21, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/627 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) 2.6.0 ### macOS Version? (Ex. mac 10.14) 10.15.6 ### Steps to reproduce 1. Make a request that with json in the body or response 2. Navigate to request/response pane and select "Body/JSON" as the format 3. Adjust the pane height to make the scrollbar visible 4. Try to scroll the pane content with mouse wheel ### Expected behavior The content is scrollable with mouse wheel. ### Actual behavior The content is scrollable only by dragging the scrollbar. Note that this problem is specific to Body/JSON case - if you select e.g. "Raw", "Header" or Body/Tree View, the content is scrollable with mouse wheel as expected. ### Screenshots (optional) <img width="1078" alt="Screen Shot 2020-09-21 at 22 31 39" src="https://user-images.githubusercontent.com/803905/93818736-09829e00-fc5b-11ea-9bbf-425901b5cdbd.png">

kerem added the

bug

label

2026-03-03 19:20:25 +03:00

kerem commented

2026-03-03 19:20:26 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Sep 22, 2020):

I use mouse wheel all the time but I couldn't reproduce your issue 🤔

Can you try each Scroller behavior option in System Preference -> General, let see how it helps?
Just wondering: Does the bug only happen all time or just when you collapse some nodes (like your screenshot) 🤔

@NghiaTranUIT commented on GitHub (Sep 22, 2020): I use mouse wheel all the time but I couldn't reproduce your issue 🤔 ![2020-09-22 08 24 43](https://user-images.githubusercontent.com/5878421/93836585-7161d480-fcad-11ea-870b-7033cefcba22.gif) 1. Can you try each Scroller behavior option in System Preference -> General, let see how it helps? 2. Just wondering: Does the bug only happen all time or just when you collapse some nodes (like your screenshot) 🤔 <img width="780" alt="Screen_Shot_2020-09-22_at_8_05_00_AM" src="https://user-images.githubusercontent.com/5878421/93836519-437c9000-fcad-11ea-892a-7162f051d689.png">

kerem commented

2026-03-03 19:20:26 +03:00

Author

Owner

@grigorye commented on GitHub (Sep 22, 2020):

Huh... Now I can not reproduce either. :-( Did no changes in the system configuration... Re: collapsed nodes - I recall that I checked it multiple times and with multiple calls - it was consistently reproducible in requests/responses bodies - as I described in "Actual behavior". I'm not sure about that, but I upgraded to 2.7.0 since that moment/so probably relaunch of the app did resolve it.

Feel free to close this issue for now. Will try to take a note if it happens again.

@grigorye commented on GitHub (Sep 22, 2020): Huh... Now I can not reproduce either. :-( Did no changes in the system configuration... Re: collapsed nodes - I recall that I checked it multiple times and with multiple calls - it was consistently reproducible in requests/responses bodies - as I described in "Actual behavior". I'm not sure about that, but I upgraded to 2.7.0 since that moment/so probably relaunch of the app did resolve it. Feel free to close this issue for now. Will try to take a note if it happens again.