microsoft / microsoft/vscode-azureresourcegroups
[CoR] Chat does not automatically scroll to approval requests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
VS Code Insider: 1.133.0-insider
Build Version: 0.12.8-alpha.0
Repro Steps:
- Create a new Azure Project.
- Generate a project plan.
- Wait for a tool approval prompt to appear.
- Observe the Chat panel.
Expect:
Approval requests should be automatically brought into view, or a clear notification should indicate that user action is required.
Actual:
When an approval request is generated in Chat, the approval card may appear outside the visible Chat area and is not automatically brought into view. Users must manually scroll down or click the "Scroll to Latest Message" button to discover and respond to the request.
More Info:
- This issue is intermittent and does not reproduce consistently.
- This issue is not specific to project plan generation and may affect any workflow step that requires user approval through the Chat panel. If the approval request is out of view, users may not realize that the workflow is waiting for input and may assume it is stuck.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the project-plan workflow in the VS Code Chat panel and inspect how approval requests are rendered and brought into view. Verify the behavior with approval prompts that appear below the visible area; done means the request is automatically visible or a clear notification tells the user action is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100