Word Wrap feature not working correctly

[mkhlz]

Type: Bug

Make a simple text file with lorem ipsum verbiage and fill a paragraph. Turn on word wrap feature. Keep lines at 70 characters. Shorten the viewport to overflow the line character limit. Now pick any random line and place a few characters at the end of the line. If the line ends with a set of continuous characters (NOT carriage return, example a word or a stream of dots or dashes) the wrapping hides the left side of the viewport by a few pixels

VS Code version: Code 1.71.2 (74b1f97, 2022-09-14T21:03:37.738Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

[vscodenpa]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[alexdima]

@mkhlz Could you please share sample text and a screenshot demonstrating the problem? Have you tried editor.wrappingStrategy: "advanced"?

[mkhlz]

Hey! Sorry I should have put a screenshot. Some more context:

Here's the normal flow when you go to the next line after carriage return. The gutter and viewport looks as expected. All good no problems here.

But now let me end the line without the carriage return. In this case I'll simply add some period characters . to achieve that. Notice the gutter area gets jacked up after the caret goes to the next line.

Apologies for the lack of info. This should clear things up. Let me know if you need more info.

Also, let me check if the option you suggested works.

By the way, there is a workaround hack. Just fix the line width to be less than the viewport. And in the wrap settings, use wordWrapColumn or bounded but like I said the original bug still exists

[mkhlz]

I can confirm that "editor.wrappingStrategy": "advanced" does not work @alexdima

[mkhlz]

closing this issue and making a new one, cuz of non-response

[alexdima]

@mkhlz Does this reproduce when disabling the gitlens extension?

[mkhlz]

No, the issue is non-reproduceable after disabling the git lens extension. Although I really need that extension :(

In this case, how are things handled? By the extension developer, or VSCode? @alexdima

[alexdima]

Let's track in #32856