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
Environment (please complete the following information):
OS (e.g., Windows 10): Windows 11
Extension version (e.g., 1.2.3): 2.1.6
Describe the bug: When I launch a debug session with Edge, it opens up Edge in debugging as expected. I then have found two ways to access Edge DevTools and they are behaving differently.
When accessed via "Open Browser Devtools" through the debug bar in VS Code, it opens the Edge DevTools tab. Source mapping for my CSS files works great on the Elements tab. On the Console tab, none of my logs have a file name / link mentioned. So that source mapping is not working.
If I instead access it via Edge DevTools extension in the side bar, and then click "Attach and open Microsoft Edge Tools" next to my browser window, it closes the other Edge DevTools and opens this one. They are mostly identical except in this one, the Console tab properly shows file links and the source mapping works. The elements tab when clicking on a CSS Stylesheet, gives errors. Which is identical to Error while opening CSS file in editor #787
Repro steps:
Launch Edge via Debugger in VS Code
Try hitting the "Open Browser DevTools" button in the debug bar
Observe that the Console tab has no files/source mapping
Observe that in the Elements tab, you can see and click on stylesheets and it will open in the VS Code Editor.
Now go to the Edge DevTools extension window in the sidebar/activity pane.
Hover over your Edge Browser Session and click "Attach and open Microsoft Edge Tools"
Observe that the Console tab now has files/source mapping and can open files in editor
Observe that in the Elements tab, if you click a stylesheet, you get error Error while opening file in editor. Could not open document. No workspace mapping was found for 'http://localhost:9001/styles/base/layout.css'.
Expected behavior: In either way of opening Dev Tools (or at least one method) you should be able to access source mapping for both JS and CSS. I shouldn't have to change DevTools depending on what I am troubleshooting.
Additional context: I will Include my launch.json, tasks.json, and webpack config to see if it offers any insight to why this is happening or if I am just doing something wrong.
Environment (please complete the following information):
Describe the bug: When I launch a debug session with Edge, it opens up Edge in debugging as expected. I then have found two ways to access Edge DevTools and they are behaving differently.
Repro steps:
Error while opening file in editor. Could not open document. No workspace mapping was found for 'http://localhost:9001/styles/base/layout.css'.
Expected behavior: In either way of opening Dev Tools (or at least one method) you should be able to access source mapping for both JS and CSS. I shouldn't have to change DevTools depending on what I am troubleshooting.
Additional context: I will Include my launch.json, tasks.json, and webpack config to see if it offers any insight to why this is happening or if I am just doing something wrong.
webpack.config.mjs:
launch.json:
tasks.json:
Method 1 of opening DevTools:
Method 2 of opening DevTools:
Method 1 blank console:
The text was updated successfully, but these errors were encountered: