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

Retain the selection after tree refresh #33371

Closed
bpasero opened this issue Aug 29, 2017 · 11 comments
Closed

Retain the selection after tree refresh #33371

bpasero opened this issue Aug 29, 2017 · 11 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority tree-views Extension tree view issues verified Verification succeeded
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Aug 29, 2017

Steps to Reproduce:

  1. install docker extension
  2. click with the mouse into the contributed explorer

=> focus is shortly removed out of the view
=> focus should stay so that keyboard interaction is possible

flicker_chrome58

@sandy081
Copy link
Member

It is not true in all custom views. Looks like this is having a command that is causing this.

@bpasero
Copy link
Member Author

bpasero commented Aug 29, 2017

Ok then it should maybe move into the docker repository.

@chrisdias
Copy link
Member

i'm refreshing the tree every second :(

@sandy081
Copy link
Member

I see may be I should retain the selection after refresh. I should have a fallback if the selected item is gone after refresh

@sandy081 sandy081 added the tree-views Extension tree view issues label Aug 30, 2017
@sandy081 sandy081 added this to the September 2017 milestone Aug 30, 2017
@sandy081 sandy081 added the feature-request Request for new features or functionality label Aug 30, 2017
@sandy081 sandy081 changed the title Contributed view: clicking into entry removes focus Retain the selection after tree refresh Aug 30, 2017
@eamodio
Copy link
Contributor

eamodio commented Sep 1, 2017

Yeah, it would be great if it was retained -- expand/collapsed state too.

While it would great for the view to do this itself, at least having a new API where the extension could attempt to maintain it would also work (though obviously more work on the part of the extension). But an API for it could be valuable in other situations where you might want to cause selection in the tree. Of course that would also have to deal with expansion too for nested things.

@sandy081 sandy081 modified the milestones: September 2017, Backlog Sep 25, 2017
@eamodio
Copy link
Contributor

eamodio commented Sep 25, 2017

Noooo - Backlog 😢 Is there another way around this? Right now an extension can't even maintain its selection so there is no way to get a better experience.

@sandy081
Copy link
Member

@eamodio I do not want to assign to a milestone and give false hopes. Actually I would collect the next set of features for tree views and discuss for our plan and assign the milestone.

@weinand
Copy link
Contributor

weinand commented Nov 29, 2017

I'm bumping the severity of this since it makes the tree very difficult to use for users.

@weinand weinand added the important Issue identified as high-priority label Nov 29, 2017
@weinand weinand added bug Issue identified by VS Code Team member as probable bug and removed feature-request Request for new features or functionality labels Nov 29, 2017
@weinand
Copy link
Contributor

weinand commented Nov 29, 2017

This is a severe bug not a feature.

@sandy081 sandy081 modified the milestones: Backlog, November 2017 Nov 30, 2017
@sandy081
Copy link
Member

sandy081 commented Dec 3, 2017

Fixed by cb926d5

@sandy081 sandy081 closed this as completed Dec 3, 2017
@mjbvz mjbvz added the verified Verification succeeded label Dec 6, 2017
@weinand
Copy link
Contributor

weinand commented Dec 11, 2017

While verifying the fix with my extension, I've noticed that the selection is only retained if the label of the tree node does not change. If the label changes (e.g. because one part of it reflects a status), the selection is still lost.

I've created issue #40018 for this.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 17, 2018
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 important Issue identified as high-priority tree-views Extension tree view issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants