Skip to content
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

Scroll bar and minimap arrive at the start / end before reaching the first or last line #22759

Closed
Tekbr opened this issue Mar 16, 2017 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@Tekbr
Copy link

Tekbr commented Mar 16, 2017

  • VSCode Version: 1.11.0 - insiders
  • OS Version: Windows 10

-- Sorry for the English, I used Google Translator --

Steps to Reproduce:

Settings "editor.wordWrap": "on"

1.Take a file with many lines. This example was using angular.js 1.6.3
2.Scroll down the page using the minimap or the scroll bar to the end.
3.Note that the minimap or scrollbar has come to an end, but we still have more rows.
4.Go back to the beginning using the minimap or the scroll bar to start.
5.See that the minimap or the scroll bar has reached the beginning but we still have more lines.

Atom works properly.

Note: I know that VSCode has an empty space at the end in the files (this is cool), I believe this has no influence.

scroll1

@alexdima
Copy link
Member

For very large files we artificially inflate the height of the slider such that it is easy to grab via the mouse.

This is implemented in a quite crude way, where the slider height is inflated in both vertical directions (up and down). This might lead to the slider appearing to be all the way to the bottom, even if this is not the case.

@alexdima alexdima added the bug Issue identified by VS Code Team member as probable bug label Apr 26, 2017
@alexdima alexdima added this to the Backlog milestone Apr 26, 2017
@alexdima
Copy link
Member

alexdima commented Jun 6, 2017

Duplicate of #6710

@alexdima alexdima closed this as completed Jun 6, 2017
@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 6, 2017
@Tekbr
Copy link
Author

Tekbr commented Jun 9, 2017

Thank you so much @alexandrudima . 👏 👏 😄

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants