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

Scrolling in tree while a USS file is opening causes "snap" back to opened item #2486

Closed
traeok opened this issue Sep 28, 2023 · 2 comments · Fixed by #3350
Closed

Scrolling in tree while a USS file is opening causes "snap" back to opened item #2486

traeok opened this issue Sep 28, 2023 · 2 comments · Fixed by #3350
Assignees
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases

Comments

@traeok
Copy link
Member

traeok commented Sep 28, 2023

Describe the bug

If you scroll in the USS tree while a USS file is being opened, sometimes the tree will "snap" the user's view back to the opened item. This might be more obvious because we are pulling USS files from the mainframe once they are clicked, and this could be an issue with tree views in general in VS Code.

To Reproduce

  1. Execute a search filter in the USS tree - specifically, try to filter down to a directory with a lot of files/folders (so there is a scroll bar).
  2. Click on a USS file to open it, and immediately after, start scrolling up the tree so that the file becomes out of view.
  3. Notice that VS Code will jump back to the opened USS file once it shows in the editor.

Expected behavior

The tree should not snap back to the location of the USS file, and the "visible region" of the tree should stay as-is.

Desktop (please complete the following information):

  • Zowe Explorer Version: 2.11
@traeok traeok added the bug Something isn't working label Sep 28, 2023
@github-actions
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@JTonda JTonda added priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases labels Oct 10, 2023
@t1m0thyj t1m0thyj moved this from New Issues to Low Priority in Zowe Explorer for VS Code Dec 26, 2023
@traeok

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

2 participants