-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Configuring a non-existing browser alias fails silently #223349
Comments
I think this might be reported as sindresorhus/open#272 and misses a fix or workaround. If someone has an idea, either by contributing to https://github.com/sindresorhus/open or seeing what we can do here: vscode/src/vs/platform/native/electron-main/nativeHostMainService.ts Lines 510 to 538 in 00374b8
|
This bug has been fixed in the latest release of VS Code Insiders! @TylerLeonhardt, you can help us out by commenting If things still don't seem right, please ensure you're on version 36e4ddb of Insiders (today's or later - you can use Happy Coding! |
It appears that this is fixed by opening the default instead of what is configured. That makes sense to me. |
Testing #220989
Not sure if this is possible, but I set the
workbench.externalBrowser
tofirefox
even though I don't have Firefox... then I tried to open something and nothing happened. I was confused because I thought I had Firefox installed, but I guess I remembered incorrectly!I think something like this is increasingly important in the workspace-setting level. Sure, the protection of this is behind Workspace Trust... but I don't seem to get any notification or indication that there's a setting applied that influences how VS Code opens the browser or if it's going to no-op.
Considering this setting influences things like user auth flows, I think we should try to do something here. I was surprised that no browser was opened when I attempted to log in to a GitHub extension... which makes sense if this setting is set to something invalid.
The text was updated successfully, but these errors were encountered: