cursor appearing on wrong position when beyond 300 in php file

[nbapat43]

• VSCode Version: Code 1.10.1 (653f873, 2017-03-02T00:33:15.706Z)
• OS Version: Windows_NT ia32 10.0.14393
• Extensions:

Extension	Author	Version
csharp	ms-vscode	1.6.2
debugger-for-chrome	msjsdiag	2.4.2
debugger-for-ios-web	msjsdiag	0.1.2

---

Steps to Reproduce:

1. create a .php file and create a line of code that goes over 300 columns/ characters in the text editor. You will notice that the cursor is partially over the the next character not inbetween them
2. If you go over 900 columns/ characters in the text editor it is beyond the next character

[alexdima]

@nbapat43 I cannot reproduce. To help me reproduce, can you please:

• perhaps take a screenshot or a screen recording demonstrating the problem.
• share your entire settings (especially those around the font, or zoom level)

Thanks!

[nbapat43]

 see pic Neal Bapatनील बापट

…

---- On Wed, 08 Mar 2017 00:28:25 -0800 Alexandru Dima <notifications@github.com> wrote ---- @nbapat43 I cannot reproduce. To help me reproduce, can you please: perhaps take a screenshot or a screen recording demonstrating the problem. share your entire settings (especially those around the font, or zoom level) Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[alexdima]

@nbapat43 Thank you for the screenshot. Could you please also share your settings?

[nbapat43]

{
"php.validate.executablePath": "C:/php7/php.exe",
"workbench.welcome.enabled": false,
"php.validate.run": "onType",
"workbench.iconTheme": "vs-seti",
"editor.minimap.enabled": true,
"editor.cursorBlinking": "solid"
}

[W4RH4WK]

I encountered a similar issue when zooming using Ctrl +. The cursor was offset to the text, sometimes even right on a character.

Here are my settings from which you can see that I am using Hack as my font.

Update: I encountered this on Linux, yet was not able to reproduce it on Windows using the same font.

[alexdima]

I believe this shared the same root cause as #26151 and the fix for #26151 should also fix this issue.