Debug bar still show debug actions if tab it was attached to was closed
See original GitHub issueConfig
{
"type": "pwa-msedge",
"request": "attach",
"port": 9222,
"name": "Attach Edge",
"targetSelection": "pick",
"urlFilter": "example.com*",
"webRoot": "${workspaceFolder}"
}
- Open https://example.com/target and https://example.com/other in browser
- Start debug with config above and pick https://example.com/target from list
- Close tab with https://example.com/target
- Call Stack section is empty but debug bar still has actions Pause, Step Over etc.
In this case of "targetSelection": "pick"
session should be stopped - even if I open another tab with same URL it wont be attached to it (as expected).
In case of "targetSelection": "automatic"
I would expect same behavior - close all tabs to stop debug session, but I see how some might want to leave session - new tabs would be picked up.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Debug actions pane often blocks file names #2513 - GitHub
Currently the debug actions pane is always displayed at the top center position. This often blocks the file names.
Read more >Debug tool window | IntelliJ IDEA Documentation - JetBrains
When you start a debugger session, the Debug tool window appears. ... When you close a tab, the corresponding session terminates.
Read more >IntelliJ IDEA 2017 - Missing Debug window - Stack Overflow
There was no Debug tab showing on the main window. The Debug entry in the View menu was greyed. The solution that finally...
Read more >Debug Bar - WP Engine
Debug Bar enables users to quickly diagnose issues with WordPress installs. ... more tabs available in the Debug Bar to display Actions and...
Read more >Debugging in Visual Studio Code
Once a debug session starts, the Debug toolbar will appear on the top of the editor. Debug Actions. Action, Explanation. Continue / Pause...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, got it:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --remote-debugging-port=9222
Trying to reproduce this on Windows 10 2004 with Edge. On step 2. I don’t get a picker, but a dialog
Could not connect to debug target at http://localhost:9222: Could not find any debuggable target
Is there anything else I need to configure so that Edge knows about that port?