Skip to content

Secondary Side Bar view contributions fallback to Explorer unexpectedly #249910

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

Open
samii32 opened this issue May 27, 2025 · 0 comments
Open

Secondary Side Bar view contributions fallback to Explorer unexpectedly #249910

samii32 opened this issue May 27, 2025 · 0 comments
Assignees

Comments

@samii32
Copy link

samii32 commented May 27, 2025

Problem

I tried contributing a Webview to the secondarySideBar using the newly supported "viewsContainers.secondarySideBar" field as described in PR #247899.

However, even with correct activationEvents, ID matching, and version 1.97+, the view often falls back to the explorer container with this warning:

"View container 'ChatPanel' does not exist and all views registered to it will be added to 'Explorer'."

Expectation

Since secondarySideBar is officially supported now, I expect the Webview to be consistently displayed in the right sidebar without fallback.

Environment

  • VSCode: 1.97.0
  • Extension: test
  • Package.json: using "viewsContainers.secondarySideBar" and correct view IDs

Request

Please ensure views registered to secondarySideBar are properly initialized without fallback, or document the current limitation if intended.

Thank you!

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

No branches or pull requests

2 participants