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

Search term should not be retained when closing and reopening Settings/keybindings editor #39512

Closed
sandy081 opened this issue Dec 3, 2017 · 9 comments
Assignees
Labels
*as-designed Described behavior is as designed keybindings-editor Keybinding editor issues settings-editor VS Code settings editor issues ux User experience issues
Milestone

Comments

@sandy081
Copy link
Member

sandy081 commented Dec 3, 2017

Steps to reproduce

Keyboard Shortcuts - Second Situation:

  • Open Keyboard Shortcuts / Settings editor and provide a filter
  • Close the editor and reopen it

Expected: Filter is not retained
Observed: Filter is retained

@vscodebot vscodebot bot added workbench workbench-tabs VS Code editor tab issues labels Dec 3, 2017
@sandy081 sandy081 assigned sandy081 and unassigned bpasero Dec 3, 2017
@sandy081 sandy081 added keybindings-editor Keybinding editor issues settings-editor VS Code settings editor issues ux User experience issues and removed workbench workbench-tabs VS Code editor tab issues labels Dec 3, 2017
@sandy081
Copy link
Member Author

sandy081 commented Dec 3, 2017

@bpasero What is the current expected UX behaviour in this case?

@sandy081 sandy081 added the bug Issue identified by VS Code Team member as probable bug label Dec 4, 2017
@bpasero
Copy link
Member

bpasero commented Dec 4, 2017

@sandy081 depends. we typically retain as much view state as possible when reopening a file (e.g. cursors, folding).

I would not expect that settings or keybindings editor preserve the state of the filter though.

@sandy081 sandy081 added this to the November 2017 milestone Dec 4, 2017
@Tekbr
Copy link

Tekbr commented Dec 5, 2017

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

@sandy081 I do not think you got what I said !!

It is not to save what I researched in the field when I close the editor. (Must be kept as is)

Not to save anything !!

What it is to change: What I said is that it still saves when you open settings, search something, close the settings tab and reopen again.

When closing the editor it really should not bring anything that was previously searched.

Let me know if you get it now !! Or if Google Translator betrayed me again.

@sandy081
Copy link
Member Author

sandy081 commented Dec 5, 2017

@Tekbr I think the summary/description of this issue aligns to what you mentioned in above comment.

@Tekbr
Copy link

Tekbr commented Dec 5, 2017

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

@sandy081 Uhmm .. I put a gif tried to explain ...

settings-key

Note: If Settings or Key are open when Reopening the VSCode these can keep what was searched.

@Tekbr I think the summary/description of this issue aligns to what you mentioned in above comment.

Anyway, it gets a boost. I think translation confused me with what @bpasero wanted to say.

Sorry for the misunderstanding. 😊 😊

@sandy081 sandy081 modified the milestones: November 2017, December 2017 Dec 6, 2017
@sandy081 sandy081 modified the milestones: January 2018, Backlog Jan 31, 2018
@sandy081
Copy link
Member Author

Filters are part of the state we retain when settings/keybindings editor are closed and opened. Closing this as designed.

@sandy081 sandy081 added *as-designed Described behavior is as designed and removed bug Issue identified by VS Code Team member as probable bug labels Sep 19, 2018
@Tekbr
Copy link

Tekbr commented Sep 19, 2018

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

@sandy081 I still see with a problem. For a comparison, Atom does not keep the information after we close the Settings tab. I hope that in the future it will be changed.
If I closed the tab I do not want to search for what was typed.

@sandy081
Copy link
Member Author

I see Atom does it that way. But we have this behaviour for a long time and it is good (not many complaints). Not sure if I would like to change the behaviour now which is not buggy.

@Tekbr
Copy link

Tekbr commented Sep 20, 2018

-- Sorry for the English, I used Google Translator --
@sandy081 All right ... Anyway thanks for the feedback. 👍

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed keybindings-editor Keybinding editor issues settings-editor VS Code settings editor issues ux User experience issues
Projects
None yet
Development

No branches or pull requests

3 participants