starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 17:26:03 +03:00

[GH-ISSUE #965] Textarea display problem in super hi-dpi #335

New issue

Closed

opened 2026-03-16 14:45:56 +03:00 by kerem · 6 comments

kerem commented

2026-03-16 14:45:56 +03:00

Owner

Originally created by @RickoNoNo3 on GitHub (Jun 29, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/965

While I was using postwoman in chrome, I found a problem: all of textareas (with linenumber) undisplayed.
(only happened in chrome/new edge, no ff/old edge)

You will easily reappear the problem:
make your screen dpi in a super high mode, such as 1920x1080 with 150% scales. And switch to POST method in the postwoman. Then check raw input. you will see that textarea of raw request body has been undisplayed.

Magically, when I changed browser display scale (ctrl + as you know). In any way, the textarea redisplayed.

Originally created by @RickoNoNo3 on GitHub (Jun 29, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/965 While I was using postwoman in chrome, I found a problem: **all of textareas (with linenumber) undisplayed**. (only happened in chrome/new edge, no ff/old edge) You will easily reappear the problem: make your screen dpi in a super high mode, such as 1920x1080 with 150% scales. And switch to POST method in the postwoman. Then check raw input. you will see that textarea of raw request body has been undisplayed. Magically, when I changed browser display scale (ctrl + as you know). In any way, the textarea redisplayed. ---- ![issue](http://rickonono3.top/postwoman.1.jpg)

kerem

2026-03-16 14:45:56 +03:00

closed this issue
added the
need information
label

kerem commented

2026-03-16 14:46:12 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 30, 2020):

@RickoNoNo3 I tried to reproduce the issue at my end but I couldn't. Can you tell a little more about your device. which operating system? Chrome version? etc..

@liyasthomas commented on GitHub (Jun 30, 2020): @RickoNoNo3 I tried to reproduce the issue at my end but I couldn't. Can you tell a little more about your device. which operating system? Chrome version? etc.. ![image](https://user-images.githubusercontent.com/10395817/86070639-c6b98b80-ba9a-11ea-893f-ac3d76e42b19.png) ![image](https://user-images.githubusercontent.com/10395817/86070475-76422e00-ba9a-11ea-8ff4-25c117017dfe.png)

kerem commented

2026-03-16 14:46:17 +03:00

Author

Owner

@RickoNoNo3 commented on GitHub (Jun 30, 2020):

@liyasthomas I use Chrome 83.0.4103.116 (latest) on Windows 10 2004. Screen: 1920x1080 (150% as 1280x720)

I tried more about how to make it reappeared and noticed:

In 100% default scaling of my Chrome, document.body.clientWidth shows 1020, with issue
In 90% scaling(1134), with issue
In l/e 80%(1275), no issue
In g/e 110%(927), no issue
In media keyword triggered, no issue
When textareas are undisplayed, adjusting the zoom to safe scaling on the same page will make them show.
Once textareas are displayed, no operations can make it restored to undisplay.

These conclusions are established, unless you reload a textarea(maybe turn off raw input and check it again). reloading a textarea has the same behavior with reloading the page.

So in my mind, this issue appears in a kind of environment with specific width. And it is a problem that occurs when generating textarea elements (not related to css).

btw body.clientWidth in default scaling of firefox is 1280 while in Chrome is 1020. The true width of 150% of 1920x1080 is indeed 1280. So my Chrome has an unexpected over zooming (bigger text as well). Edge too.

@RickoNoNo3 commented on GitHub (Jun 30, 2020): @liyasthomas I use Chrome 83.0.4103.116 (latest) on Windows 10 2004. Screen: 1920x1080 (150% as 1280x720) I tried more about how to make it reappeared and noticed: - In 100% default scaling of my Chrome, `document.body.clientWidth` shows `1020`, **with issue** - In 90% scaling(`1134`), **with issue** - In l/e 80%(`1275`), no issue - In g/e 110%(`927`), no issue - In media keyword triggered, no issue - When textareas are undisplayed, adjusting the zoom to safe scaling on the same page will make them show. - Once textareas are displayed, no operations can make it restored to undisplay. These conclusions are established, unless you reload a textarea(maybe turn off raw input and check it again). reloading a textarea has the same behavior with reloading the page. So in my mind, this issue appears in a kind of environment with specific width. And it is a problem that occurs when generating textarea elements (not related to css). btw `body.clientWidth` in default scaling of firefox is `1280` while in Chrome is `1020`. The true width of 150% of 1920x1080 is indeed `1280`. So my Chrome has an unexpected over zooming (bigger text as well). Edge too.

kerem commented

2026-03-16 14:46:22 +03:00

Author

Owner

@RickoNoNo3 commented on GitHub (Jun 30, 2020):

nonono, not just page client width, I cannot get it appeared by resizing my browser window to the "problem width". Instead, it still make a wrong in 90% and 100% scaling no matter how big the window is.
Maybe It is directly related to the total width of the screen? or the dpi?

@RickoNoNo3 commented on GitHub (Jun 30, 2020): nonono, not just page client width, I cannot get it appeared by resizing my browser window to the "problem width". Instead, it still make a wrong in 90% and 100% scaling no matter how big the window is. Maybe It is directly related to the total width of the screen? or the dpi?

kerem commented

2026-03-16 14:46:27 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jul 1, 2020):

Noted. Looking into it.

@liyasthomas commented on GitHub (Jul 1, 2020): Noted. Looking into it.

kerem commented

2026-03-16 14:46:32 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jul 5, 2020):

I guess we can ignore this UI issue since it's only reproducible in such an edge case of super-high dpi. Let me know if you it is reproducible in normal situations.

@liyasthomas commented on GitHub (Jul 5, 2020): I guess we can ignore this UI issue since it's only reproducible in such an edge case of super-high dpi. Let me know if you it is reproducible in normal situations.

kerem commented

2026-03-16 14:46:37 +03:00

Author

Owner

@RickoNoNo3 commented on GitHub (Jul 5, 2020):

You are right. It works well to set a different zoom ratio as default of Chrome.

@RickoNoNo3 commented on GitHub (Jul 5, 2020): You are right. It works well to set a different zoom ratio as default of Chrome.

kerem referenced this issue

2026-03-17 00:15:24 +03:00

[PR #335] [CLOSED] Improved readability of CODE_OF_CONDUCT.md #2561