-
Notifications
You must be signed in to change notification settings - Fork 854
Cursor off by one or more character spaces #2985
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
Comments
Seeing the same issue on Ubuntu w/ Gnome DE linux 4.13.0-36-generic / x64 |
same issue on arch linux 4.15.3-2-ARCH running i3wm |
Can you guys update to the latest Postman app (6.1.4) and see if it is happening. Thanks |
I see this happening in v6.1.4 as well. |
@venkatcc are you on Windows ? |
@prashantagarwal Yes, I'm. |
I'm still seeing this issue - the font being used is NOT picking up the system monospace font. The font in the editor isn't even monospace. |
Issue seen in v6.2.3 as well. |
Same issue on latest version |
The issue is still seen in v6.5.3. Tested on Windows 10. |
I'm seeing this in an up to date Manjaro install. 6.6.0-1 from aur/postman-bin. Previous versions had it as well. |
+1 on windows 10. Postman 6.7.3. |
The problem exists in Postman v7.0.7 (on Windows 10) as well. |
Still in v7.2.2 (on Windows 10). |
Solved this problem in Postman v7.6.0 |
@venkatcc I modified the postman font, this problem is gone, on ubuntu. |
Problem still exists on Version 7.8.0 out of the box @Axzc where do i change the font? I only found a setting for the font size (Settings->General->User Interface) |
this fucking issue last for 3 years, lose patience for postman |
@pythoneer in /Postman/app/resources/app/js/requester.css search .editor.ace_editor |
@Axzc modify to what?
|
@yrong change to the appropriate font |
@Axzc That did work and Thanks. My previous assumption is that if any font exists in fc list should work and seems not, need to keep |
Postman v7.10.0 on Windows 10 still has this issue. |
Closing this issue as we haven't been able to replicate this. Please open a new issue with replication steps if needed. |
I investigated this problem a little bit deeper and it looks like that in my case the problem stems from a bug in the noto font configuration on arch i have installed on my system https://github.com/googlefonts/noto-fonts/issues/1128 also https://bugs.archlinux.org/task/64083 |
@a85 have you ever read previous discussion? how dare you say unable to replicate? The root cause is that default font configuration is not proper in most linux releases.
|
I can reproduce this every time. I'm on Windows 10, and earlier suggestions to mess around with default font configuration on Linux to get this working right are not applicable on Windows (since I couldn't find the equivalent configuration files or the equivalent configuration settings). Today, I removed my 7.10.0 installation and installed 7.12.0 and I still see the issue. I've attached a video showing the problem. As I start typing the second key-value pair, you can see the cursor moving ahead, and this makes any typing impossible. If you'd like to repoduce, I suggest trying the exact length strings I'm using in the video demonstration. Shorter length key-value pairs may not exhibit the problem. And other length pairs may also exhibit the problem, but I've been testing with this pair because I know this always exhibits the problem. |
The reason is postman cannot find font.so use another one,but their weight is different.I had install font Menlo-Regular.ttf and Monaco-Linux.ttf.At last It works. |
looks like even the workaround from @Axzc does not work anymore in 7.20.1 |
Same issue on latest version |
This has been fixed as part of |
@pankajk07 can confirm, this fixed it for me – thank you very much to all involved! |
Yes!! It indeed is fixed!! Thanks. |
It still reproduces on v9.1.1 (Windows 10) |
Still it is there, in chromeos, chrome browser only. |
@Sebastian23 same issue here(win10, v9.5.0) |
This actually works. Thanks a lot! :) |
Thank you! This worked for me on ChromeOS. |
Steps to reproduce the problem:
A video showing the behavior: https://www.youtube.com/watch?v=rk5Mnl5t-S8
You'll see that when I start typing the second key/value pair, the cursor 'races' ahead from where the characters are being typed.
Note: When I tried key/value pairs of shorter lengths, I did not see this issue. Can't explain the difference in behavior.
For example, the following does not have an issue:
{"key1":"value1", "key2":"value2", "key3":"value3", "key4":"value4", "key5":"value5", "key6":"value6", "key7":"value7", "key8":"value8", "key9":"value9"}
But this does:
{"email_address":"[email protected]", "first_name":"first-name"}
The text was updated successfully, but these errors were encountered: