Closed
Description
- VSCode Version: 1.48.2
- OS Version: Windows
Steps to Reproduce:
The "VS Code - Microsoft Edge (Chromium) Tools" extension development is partially broken, previously we were able to see console errors and associated resources but after we migrated to the new webview protocol it does not work anymore. Webview content gets redendered correctly but debugging/inspecting is broken. I think this is associated to using iframes inside a webview, I set up a small repro app that shows what I'm seeing.
- Clone the following repository which contains a Simple Repro App (Based on the sample-webview cat application):
https://github.com/vidorteg/webview-context-lost - npm install && npm run compile
- Open VSCode > Debug > Run Extension
- Run the Cat Coding: Start cat coding session to create the webview.link to image
- Verify that the view also shows an iframe embedded in the webview (with some content)link to image
- Open Developer Tools to debug the webview. link to image
Expected
- Should be able to select HTML elements inside the iframe
- Should be able to see console context (errors and warnings)
- Should be able to see resources associated with the iframe
All this is expected based on what is stated in here:
https://code.visualstudio.com/api/extension-guides/webview#inspecting-and-debugging-webviews
Actual
- Cannot see HTML components in the Elements View or select them using the overlay.link to image
- An error is thrown inside the script loaded in the webview but it is not shown on the Devtools Console (or anywhere) link to image
- Resource associated with the iframe (inspector.html) is not shown in the Devtools link to image
Does this issue occur when all extensions are disabled?: Yes