[GH-ISSUE #266] [BUG] [UI] [Mobile] Get results not scrollable. #90

Closed
opened 2026-03-16 13:20:30 +03:00 by kerem · 6 comments
Owner

Originally created by @AtomicMaya on GitHub (Nov 5, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/266

Originally assigned to: @hosseinnedaee on GitHub.

Describe the bug
When GETting a larger quantity of data, the Results area does not allow scrolling (the page gets scrolled instead).

To Reproduce
Steps to reproduce the behavior:

  1. On Mobile, go to PW
  2. Make a GET request, where the received data exceeds the number of lines in the text area (tried with 2749, because I like breaking things).
  3. Scroll down to the Results area
  4. Try scrolling the Text Area.

Expected behavior
Scroll should be deferred to Text Area instead of page.

Screenshots
photo_2019-11-05_10-55-34

Smartphone (please complete the following information):

  • Device: Xiaomi Redmi Note 7
  • OS: Android 9.something
  • Browser stock, Chrome, Firefox Focus, Opera
  • Version latest
Originally created by @AtomicMaya on GitHub (Nov 5, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/266 Originally assigned to: @hosseinnedaee on GitHub. **Describe the bug** When GETting a larger quantity of data, the _Results_ area does not allow scrolling (the page gets scrolled instead). **To Reproduce** Steps to reproduce the behavior: 1. On Mobile, go to PW 2. Make a GET request, where the received data exceeds the number of lines in the text area (tried with 2749, because I like breaking things). 3. Scroll down to the _Results_ area 4. Try scrolling the Text Area. **Expected behavior** Scroll should be deferred to Text Area instead of page. **Screenshots** ![photo_2019-11-05_10-55-34](https://user-images.githubusercontent.com/18284503/68197685-ee635d00-ffba-11e9-95b3-1915939c9816.jpg) **Smartphone (please complete the following information):** - Device: Xiaomi Redmi Note 7 - OS: Android 9.*something* - Browser stock, Chrome, Firefox Focus, Opera - Version *latest*
kerem 2026-03-16 13:20:30 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@hosseinnedaee commented on GitHub (Nov 8, 2019):

I checked it on the same device and it works fine for me (Chrome & Opera).

<!-- gh-comment-id:551383502 --> @hosseinnedaee commented on GitHub (Nov 8, 2019): I checked it on the same device and it works fine for me (Chrome & Opera).
Author
Owner

@liyasthomas commented on GitHub (Nov 8, 2019):

Normal responses with LOC < 100 works fine.
Huge payload breaks HighlightJS render. Issue will persist until syntax highlighting is migrated to ace.

<!-- gh-comment-id:551385149 --> @liyasthomas commented on GitHub (Nov 8, 2019): Normal responses with LOC < 100 works fine. Huge payload breaks HighlightJS render. Issue will persist until syntax highlighting is migrated to ace.
Author
Owner

@hosseinnedaee commented on GitHub (Nov 8, 2019):

I will work on it.

<!-- gh-comment-id:551445576 --> @hosseinnedaee commented on GitHub (Nov 8, 2019): I will work on it.
Author
Owner

@liyasthomas commented on GitHub (Nov 8, 2019):

Currently, response is syntax highlighted in <pre><code> tags for highlightJS implementation. Remove hljs and implement alternative (such as ace) that supports textarea highlighting

<!-- gh-comment-id:551446776 --> @liyasthomas commented on GitHub (Nov 8, 2019): Currently, response is syntax highlighted in `<pre><code>` tags for highlightJS implementation. Remove hljs and implement alternative (such as ace) that supports textarea highlighting
Author
Owner

@hosseinnedaee commented on GitHub (Nov 8, 2019):

Currently, response is syntax highlighted in <pre><code> tags for highlightJS implementation. Remove hljs and implement alternative (such as ace) that supports textarea highlighting

Okay

<!-- gh-comment-id:551449904 --> @hosseinnedaee commented on GitHub (Nov 8, 2019): > Currently, response is syntax highlighted in `<pre><code>` tags for highlightJS implementation. Remove hljs and implement alternative (such as ace) that supports textarea highlighting Okay
Author
Owner

@AtomicMaya commented on GitHub (Nov 12, 2019):

Yup, This was fixed !

<!-- gh-comment-id:552842847 --> @AtomicMaya commented on GitHub (Nov 12, 2019): Yup, This was fixed !
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#90
No description provided.