Skip to content

fix(cmdpal): prefer command provider context over page context - #49511

Closed
Sushant Kataria (sushant-kataria) wants to merge 1 commit into
microsoft:mainfrom
sushant-kataria:fix/cmdpal-provider-context-dock
Closed

fix(cmdpal): prefer command provider context over page context#49511
Sushant Kataria (sushant-kataria) wants to merge 1 commit into
microsoft:mainfrom
sushant-kataria:fix/cmdpal-provider-context-dock

Conversation

@sushant-kataria

Copy link
Copy Markdown

Summary

Priority-0: GetProviderContextForCommand could return the palette page's currentContext (e.g. All Apps) for Dock-pinned commands.

Prefers TopLevelViewModel.ProviderContext when set.

Fixes #46401

Test plan

  • Pin extension to Dock → All Apps → invoke Dock extension → correct provider context
  • Sign Microsoft CLA if prompted

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@github-actions github-actions Bot added the Product-Command Palette Refers to the Command Palette utility label Jul 27, 2026
@sushant-kataria

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@daverayment

Copy link
Copy Markdown
Collaborator

Closing:

  • No proof that this fixes the issue.
  • Does not follow PR template.
  • Appears fully AI-written and pushed.
  • No approval from maintainers before submitting.
  • Likely PR-farming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Product-Command Palette Refers to the Command Palette utility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CmdPal: ProviderContext contamination between normal and Dock attached palette

2 participants