We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
I tried contributing a Webview to the secondarySideBar using the newly supported "viewsContainers.secondarySideBar" field as described in PR #247899.
secondarySideBar
"viewsContainers.secondarySideBar"
However, even with correct activationEvents, ID matching, and version 1.97+, the view often falls back to the explorer container with this warning:
explorer
"View container 'ChatPanel' does not exist and all views registered to it will be added to 'Explorer'."
Since secondarySideBar is officially supported now, I expect the Webview to be consistently displayed in the right sidebar without fallback.
Please ensure views registered to secondarySideBar are properly initialized without fallback, or document the current limitation if intended.
Thank you!
The text was updated successfully, but these errors were encountered:
bhavyaus
No branches or pull requests
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:Expectation
Since
secondarySideBar
is officially supported now, I expect the Webview to be consistently displayed in the right sidebar without fallback.Environment
"viewsContainers.secondarySideBar"
and correct view IDsRequest
Please ensure views registered to
secondarySideBar
are properly initialized without fallback, or document the current limitation if intended.Thank you!
The text was updated successfully, but these errors were encountered: