Test: Chat-tab presentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start in the VS Code Agents Window with a session containing multiple chats, then follow the presentation and navigation steps in the issue using both mouse and keyboard. Verify Multiple and Single modes, tab and session synchronization, persistence after reload, focus behavior, and the absence of incorrect initial state or flicker. Done means every listed behavior works consistently.
Written by the indexing model from the issue text.
Description
Refs: https://github.com/microsoft/vscode/pull/336595, https://github.com/microsoft/vscode/pull/336794
- anyOS
- anyOS
Complexity: 3
Authors: @sandy081
Verify chat-tab presentation settings in the Agents Window.
- Open a session with multiple chats.
- From the session header menu, switch the chat presentation to Multiple.
- Verify every open chat has a tab, switching tabs selects the correct conversation, and the checked menu item matches the visible presentation.
- Switch to Single and verify tab chrome is hidden without closing chats or losing their state.
- Navigate between the chats from the Sessions list and verify the visible chat title and session header stay synchronized.
- Switch back to Multiple and verify the existing tabs and active chat are restored.
- Reload the Agents Window and verify the selected presentation persists and is applied without an incorrect initial state or visible flicker.
- Explore the menu, tab switching, closing, and focus behavior with both mouse and keyboard.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·