microsoft / microsoft/vscode-dotnettools

Active item tracking does not trake effect when switching to Solution Explorer from another view

Open
#2,182 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area-solution bug
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the Issue

Am a big fan of the Solution Explorer active item tracking (#51). One tiny UX issue though: when switching to another view (e.g. the test) and then navigating to some other file, when I switch back to the Solution Explorer, it does not show the active item, but rather the last item that was open in it. It would be great if the Solution Explorer could sync to the active item when switching back to it from another view.

Steps To Reproduce
  1. With C# dev kit 1.30.44
  2. Open two files in the Solution Explorer (A and B)
  3. With A open as the active tab, switch to e.g. the test view
  4. Use Ctrl-Tab to switch to B as the active tab
  5. Switch back to the Solution Explorer

The solution explorer still shows file A rather than B, though the latter is the active tab.

Expected Behavior

No response

Environment Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with C# Dev Kit 1.30.44 by opening files A and B, switching to another view, and using Ctrl-Tab to make B active. Start by tracing the Solution Explorer's active-item tracking; done means returning to it displays B rather than the previously shown A.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.