Closed amweiss closed 3 months ago
Can you please let me know the value of this registry key?
We will use Edge automatically if it's set as the platform default browser, but it seems like the detection is not working in your case.
Here's the output of that command:
reg QUERY HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\http\UserChoice /v ProgId
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\http\UserChoice
ProgId REG_SZ MSEdgeHTM
@connor4312 sorry for the tag, but I didn't want to start a new issue just to ask so I wanted to make sure it was seen on a closed issue.
Any chance of getting a release of vscode-js-debug-companion
to make this work? I didn't see a nightly like the vscode-js-debug
extension so I can't verify this or benefit from it yet.
I have Edge Dev set as my default browser, and this works fine from non-js-debug terminal, but not from a js-debug terminal.
@alexr00 can you share more details about the platform you're on? We don't detect Edge Dev in general on Windows. I think that's a separate issue if so.
My mistake, I thought this was for just using the default browser. I'm on Windows using WSL.
We don't naively launch the default browser because it might not be debuggable; we identify if it's Edge or (by default) Chrome and then launch that using our usual discovery.
Closing for some reverification
Describe the bug When using the Debug Terminal with VSCode in WSL remote mode, there was no obvious way to switch the browser option to Edge. I was able to make it work by using the following config:
To Reproduce Steps to reproduce the behavior:
VS Code Version:
v2024.5.217