Repository navigation
unable to navigate to the debugger page (when launched from VS Code?) #490
Description
Activity
- changed the title
[-]Debugger can't select[/-][+]unable to navigate to the debugger page (when launched from VS Code?)[/+]on Apr 2, 2019 This is by design but we should make the message more obvious.
I'm curious, do you have a use case where using the debugger in devtools is could be more convenient than the debugger from vscode? Our assumption was VSCode users would prefer the integrated VSCode debugger but we might be missing something.See the tooltip message: "This screen is disabled because it provides functionality already available in your code editor".
If you would like to try out the debugger after launching from Intellij, you can remove all query parameters from the devtools url other than the one indicating the port.Our assumption was VSCode users would prefer the integrated VSCode debugger but we might be missing something.
The main reason for disabling it was actually just a current technical limitation. There are lots of assumptions in VS Code (and probably IntelliJ) about it owning the debug session, for example when an app restarts, VS Code send breakpoints and then resume. If there are multiple debuggers, they both need to send their breakpoints before either of them unpause to avoid races. There are also assumptions that VS Code has the "true list of breakpoints" and it may overwrite/remove those added by other debuggers during a restart.
It'd be nice to resolve these issues, but some of them (like the "who resumes after a restart" one) aren't as simple as just making changes in VS Code.
That said, we could more easily ensure if you "Start without Debugging" from VS Code, that we don't run any code during restarts (etc.) and then not disable the debugger here. That would let people use devtools for the debugging if they wish.
this was an issue for the html app - closing as obsolete
studio console can't view long data.