Skip to content

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

Closed
venkatcc opened this issue Apr 29, 2017 · 39 comments · Fixed by #8601
Closed

Cursor off by one or more character spaces #2985

venkatcc opened this issue Apr 29, 2017 · 39 comments · Fixed by #8601

Comments

@venkatcc
Copy link

  1. Postman Version: 4.10.7
  2. App (Chrome app or Mac app): Postman for Windows
  3. OS details: Windows 10 Pro
  4. Is the Interceptor on and enabled in the app:
  5. Did you encounter this recently, or has this bug always been there: Started using this only recently and I've seen it since day 1.
  6. Expected behaviour: Typed characters should be input at the cursor's position.
  7. Console logs (http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/ for the Chrome App, View->Toggle Dev Tools for the Mac app):
  8. Screenshots (if applicable)

Steps to reproduce the problem:

  1. Start a POST method for some API, and click on the "Body" tab, and choose the "raw" radio-button to compose the body of the API.
  2. Start typing some text, like say JSON key/value pairs.
  3. The first few characters seem to be displayed as typed and the cursor position seems fine. But after a while, the cursor position is off by one or more character spaces. The behavior is very similar to what is described here for ATOM: https://discuss.atom.io/t/cursor-appears-to-be-displayed-one-character-to-the-right-of-its-actual-position/1452

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"}

@gerbal
Copy link

gerbal commented Mar 6, 2018

Seeing the same issue on Ubuntu w/ Gnome DE linux 4.13.0-36-generic / x64
Postman Version 5.5.2

@griffinwalker
Copy link

same issue on arch linux 4.15.3-2-ARCH running i3wm

@prashantagarwal
Copy link

Can you guys update to the latest Postman app (6.1.4) and see if it is happening. Thanks

@venkatcc
Copy link
Author

venkatcc commented Jul 3, 2018

I see this happening in v6.1.4 as well.

@prashantagarwal
Copy link

@venkatcc are you on Windows ?

@venkatcc
Copy link
Author

venkatcc commented Jul 3, 2018

@prashantagarwal Yes, I'm.

@freiguy1
Copy link

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.

@venkatcc
Copy link
Author

venkatcc commented Aug 9, 2018

Issue seen in v6.2.3 as well.

@geekysrm
Copy link

geekysrm commented Dec 5, 2018

Same issue on latest version
Ubuntu 18.04

@venkatcc
Copy link
Author

The issue is still seen in v6.5.3.

Tested on Windows 10.

@surewould
Copy link

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.

@TCB13
Copy link

TCB13 commented Feb 8, 2019

+1 on windows 10. Postman 6.7.3.

@venkatcc
Copy link
Author

The problem exists in Postman v7.0.7 (on Windows 10) as well.

@venkatcc
Copy link
Author

Still in v7.2.2 (on Windows 10).

@Axzc
Copy link

Axzc commented Sep 9, 2019

Solved this problem in Postman v7.6.0

@Axzc
Copy link

Axzc commented Sep 10, 2019

@venkatcc I modified the postman font, this problem is gone, on ubuntu.

@pythoneer
Copy link

Problem still exists on Version 7.8.0
linux 5.3.4-arch1-1-ARCH / x64

out of the box

@Axzc where do i change the font? I only found a setting for the font size (Settings->General->User Interface)

@yrong
Copy link

yrong commented Oct 14, 2019

this fucking issue last for 3 years, lose patience for postman

@Axzc
Copy link

Axzc commented Oct 28, 2019

@pythoneer in /Postman/app/resources/app/js/requester.css search .editor.ace_editor

@yrong
Copy link

yrong commented Oct 28, 2019

@Axzc modify to what?

➜  Postman-6.1.3 cat app/resources/app/js/requester.css | grep -i ".editor.ace_editor" -C 5
.editor {
  font-size: 12px;
  border: 1px solid var(--hairline-strong);
  border-radius: 3px;
  /* Search Extension Styling */ }
  .editor.ace_editor {
    font: 12px "Monaco", "Menlo", "Ubuntu Mono", "Consolas", "source-code-pro", "Cousine", monospace; }
    .editor.ace_editor .ace_gutter {
      background-color: var(--bg-secondary); }
    .editor.ace_editor .ace_content {
      background-color: var(--bg-primary); }
  .editor.empty-editor .ace_hidden-cursors {
    visibility: hidden; }
  .editor.empty-editor .ace_marker-layer .ace_active-line {
    background: transparent; }
...

➜  Postman-6.1.3 lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
➜  Postman-6.1.3 fc-list |more
/usr/share/fonts/truetype/msttcorefonts/comicbd.ttf: Comic Sans MS:style=Bold,Ne
greta,tučné,fed,Fett,Έντονα,Negrita,Lihavoitu,Gras,Félkövér,Grassetto,Vet,Halvfe
t,Pogrubiony,Negrito,Полужирный,Fet,Kalın,Krepko,Lodia
/usr/share/fonts/truetype/tlwg/TlwgTypo-Bold.ttf: Tlwg Typo:style=Bold
/usr/share/fonts/truetype/dejavu/DejaVuSerif-Bold.ttf: DejaVu Serif:style=Bold
/usr/share/fonts/truetype/arphic/uming.ttc: AR PL UMing TW MBE:style=Light
/usr/share/fonts/truetype/fonts-kalapi/Kalapi.ttf: Kalapi:style=Regular
/usr/share/fonts/truetype/fonts-gujr-extra/Rekha.ttf: Rekha:style=Medium
/usr/share/fonts/truetype/tlwg/TlwgTypewriter-BoldOblique.ttf: Tlwg Typewriter:s
tyle=Bold Oblique
/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:style=Book
/usr/share/fonts/truetype/ubuntu/UbuntuMono-RI.ttf: Ubuntu Mono:style=Italic

@Axzc
Copy link

Axzc commented Oct 29, 2019

@yrong change to the appropriate font
This is my setting in ubuntu18.04
.editor.ace_editor {
font: 12px "Ubuntu Mono", "Menlo", "Monaco", "Consolas","source-code-pro", "Cousine", monospace, monospace; }

@yrong
Copy link

yrong commented Oct 30, 2019

@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 Ubuntu Mono first

@venkatcc
Copy link
Author

venkatcc commented Nov 5, 2019

Postman v7.10.0 on Windows 10 still has this issue.

@a85
Copy link
Contributor

a85 commented Dec 1, 2019

Closing this issue as we haven't been able to replicate this. Please open a new issue with replication steps if needed.

@a85 a85 closed this as completed Dec 1, 2019
@pythoneer
Copy link

pythoneer commented Dec 1, 2019

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

@yrong
Copy link

yrong commented Dec 2, 2019

@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.

 font: 12px "Monaco", "Menlo", "Ubuntu Mono", "Consolas", "source-code-pro", "Cousine", monospace, monospace; }

@venkatcc
Copy link
Author

venkatcc commented Dec 2, 2019

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.
CursorOff.zip

@kamalaknn kamalaknn reopened this Dec 2, 2019
@ubuntu2204
Copy link

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.

@pythoneer
Copy link

looks like even the workaround from @Axzc does not work anymore in 7.20.1

@renyuntao
Copy link

Same issue on latest version
Ubuntu 18.04

@pankajk07
Copy link
Member

This has been fixed as part of v7.26. Please update your app and try it out.

@pythoneer
Copy link

@pankajk07 can confirm, this fixed it for me – thank you very much to all involved!

@venkatcc
Copy link
Author

Yes!! It indeed is fixed!! Thanks.

@Sebastian23
Copy link

It still reproduces on v9.1.1 (Windows 10)

@paramothers
Copy link

Still it is there, in chromeos, chrome browser only.
Brave browser doesnot have this cursor problem

@gkxk
Copy link

gkxk commented Dec 17, 2021

@Sebastian23 same issue here(win10, v9.5.0)
Setting -> General -> Font-family
change from "IBMPlexMono, 'Courier New', monospace" to "'Courier New', monospace".
this fixed the problem for me

@Sebastian23
Copy link

This actually works. Thanks a lot! :)

@carsonsaldanha
Copy link

carsonsaldanha commented Mar 29, 2022

@Sebastian23 same issue here(win10, v9.5.0) Setting -> General -> Font-family change from "IBMPlexMono, 'Courier New', monospace" to "'Courier New', monospace". this fixed the problem for me

Thank you! This worked for me on ChromeOS.

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

Successfully merging a pull request may close this issue.