forked from microsoft/vscode-js-debug
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: WebView2 debugging support (microsoft#264)
* WebView2 debugging support * Minimum changed needed to support `edge` debugger type, it is just an alias for `chrome`. * This change is equivalent to the launch.json `{type: 'chrome', runTimeExecutable: 'path/to/msedge.exe'}`. * Minimum change needed to support backwards compatibility with WebView2 launch debugging configurations (`useWebView`) from [vscode-edge-debug2][1]. * Adds `urlFilter` support for `chrome` `launch` requests. Follow-ups to consider: * Separate `chrome` and `edge` debugger type configurations with Edge strings. * Validate `useWebView` configuration is configured with `runTimeExecutable`. * Tests for `useWebView` configuration. * Add browser `version` support (`stable`, `beta`, `dev`, `canary`) for Microsoft Edge (Chromium) to match backwards compatibility with [vscode-edge-debug2][1]. * Deprecate `{useWebView: 'advanced'}` in favor of `{useWebView: true, urlFilter: 'bing.com'}` * Deprecate `useWebView` in favor of `webview` debugger type. [1]: https://github.com/microsoft/vscode-edge-debug * Only set filter for advanced web view debugging. This fixes an issue caught in tests where launching with a URL other than about:blank was broken because setting the launch URL happens after the target is attached, but it would never attach if the filter failed. * Addressing review feedback: Changed target from `edge` to `msedge`, removed legacy fallback port of 2015, and added '(Chromium)' suffix to Edge identifier
- Loading branch information
1 parent
7d48cb0
commit 811b2e7
Showing
8 changed files
with
61 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters