Vscode: enter key does not make new lines

[stanleyhon]

• VSCode Version: 1.5.3
• OS Version: W10 internal (MS FTE)

Steps to Reproduce:

Unclear step to reproduce.
Sometimes problem intermittent, spamming enter 10 times will sometimes unlock it and let it create new lines again. Many tabs open, complex folder open in the folder viewer.

Debugging steps taken:

• Tried different physical keyboard
• Tried onscreen keyboard
• Tried uninstalling all extensions
• Tried restart that comes with uninstalling an extension
• Tried switching tabs and typing (can type)

[mattdot]

Same issue with same configuration. My project is not as complex and just has a few nodejs files.

Found that hitting ctrl+enter can be a workaround to create some new lines.

[hoovercj]

Thank. God. I was going crazy thinking this was just me. Came here to report this issue.

I did all of the debugging steps Stanley did as well, but the only semi-reliable way to unblock this is just to hit enter a million times.

Also FTE on a Windows 10 internal build. I do have multiple keyboards installed (ENG US, ENG INTL).

Ctrl-Enter is my current attempt at living with this, but that doesn't work well -- adding a { and then trying to press ctrl+enter to get to the next line skips past the auto-inserted closing brace.

I also created a keyboard shortcut for the "enter" key to insert a line-comment just to make sure that enter presses were being properly picked up. It worked exactly as expected.

Oddly enough, when I went to write this comment the enter key wouldn't enter a new line here on github for about 3 seconds, but of course now it isn't reproing. I'm not sure if I want this to be a Windows 10 bug or a VS Code/Electron bug.

[hoovercj]

Follow-up:

OS Build: 14939.100

Consistently repros here in the Github comment box and in other text boxes around the internet (reddit comment fields, etc.). Closing and re-opening this page and clicking into the comment box exhibits the same behavior as VS Code.

I can only repro in Chrome (Version 53.0.2785.116 m) but not IE or Edge. That suggests it is a Chromium bug independent of VS Code.

[bpasero]

This is a WINDOWS bug.

[joaomoreno]

12929

The change that regressed this in Windows has been found and the fix is now being fast tracked.

[Richard-Payne]

I'm seeing this issue on Linux too.

[programmingandtea]

This is also a bug with the Mac version.

[clounie]

Same on Mac:

• macOS Sierra 10.12.3
• VS Code 1.11.0-insider

[amykapernick]

Currently using Mac OSX 10.12.5 and VS Code Version 1.13.1 and getting the same issue

[RichardLindhout]

Mac OSX 10.12.6 and VS Code Version 1.17.2 did have this when doing 'yarn start' in the integrated terminal.