You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing a VS Code extension and looking to invoke await vscode.commands.executeCommand('vscode-edge-devtools.launch'); with a specific URL like https://example.com from my extension.
However, when I execute the above command, it is opening a static HTML page.
Is there a way to pass a custom URL to open to the above command?
Is there a way I can stop Edge: DevTools window from opening? I only want to open browser window.
AB#55932240
The text was updated successfully, but these errors were encountered:
For #1
I initially thought this could be #2416, but it does not seem to be the case as #2416 does not repro on the latest version. I think you are talking about the contribution points, at least programatically it should be possible to pass arguments such as the url. So I'll bring this to the team and see what I can do
For #2
Unfortunately no. Features as headless mode, which screencast the browser content are designed to serve as a visual guide for developers, and only support a minimal set of features that the browser supports, showing the browser without the devtools might mislead users who might believe they have a full working browser embedded in vscode. For more advanced debugging or for people who have multiple screens we suppport the non-headless mode which is a full browser.
Yes for #1, I am looking for an ability to programmatically pass the URL as a parameter to launch call. Something like await vscode.commands.executeCommand('vscode-edge-devtools.launch', { url: 'https://example.com' });
I am writing a VS Code extension and looking to invoke
await vscode.commands.executeCommand('vscode-edge-devtools.launch');
with a specific URL likehttps://example.com
from my extension.However, when I execute the above command, it is opening a static HTML page.
AB#55932240
The text was updated successfully, but these errors were encountered: