Graphical bug after VS Code update 1.75.0 on <C-u> <C-d>
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
When using <C-u> and <C-d>, the cursor appears in the place where it will move after using the command and it turns out that you can see on the screen 2 cursors for a very short period. I think its a problem in out of sync cursor movement and scroll view
To Reproduce
Steps to reproduce the behavior:
- Select version 1.75.0
- Use
<C-u>and<C-d> - Check this graphic bug
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Video slow 0.25 on 1.75.[0/1]
https://user-images.githubusercontent.com/62308020/217838645-a6d2d86a-4636-4ed2-911a-0ed380c61a95.mp4
Video slow 0.25 on 1.74.3
https://user-images.githubusercontent.com/62308020/217844544-b6ffd832-2df3-4f6e-ac9d-0edaa3c63b71.mp4
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.24.3
- VSCode version: 1.75.1
- OS: Windows 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the transient second-cursor display in VSCodeVim 1.24.3 with VS Code 1.75.1 on Windows 10, using and ; compare the behavior with VS Code 1.74.3. Trace the cursor movement and scrolling behavior from the relevant extension entry points, if identified, and consider the issue done when the extra cursor no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100