Additional Debugging Support for Injected Scripts

[AndrewMore1]

Is your feature request related to a problem? Please describe.
I am currently struggling to debug problems with scripts that have been added to the webbrowser via the AddScriptToExecuteOnDocumentCreated. As it currently stands this code is run in a blackbox which provides no feedback. There are no errors, no logs, no messages, no exceptions, which makes debugging very challenging.

I have similar issues with debugging code injected via the ExecuteScript API

Describe the solution you'd like and alternatives you've considered
I'd like to see any scripts injected or run added to a section in the Source tab that lists these scripts, and allows break points to be set against them.

AB#31335433

[champnic]

Issues #307 and/or #609 look like they may be related and be able to help, but this sounds like you are looking for more DevTools support for the executed script. I've added this scenario to our backlog. Thanks!

[jasonstephen15]

@AndrewMore1 - You can also point AddScriptToExecuteOnDocumentCreated to a dedicated script file, and set breakpoints there, that way it isn't that much of a black box. Please see this document to do so.

Closing this for now, but let us know if theres anything else we can do to help!

[ukandrewc]

These extensions automate that process: https://github.com/ukandrewc/WebView2.Winforms.JSHelper

[hunkydoryrepair]

capturing the javascript console is important to us, too. Looks like we have some devtools techniques to do it, but it involves at least 3 different handlers.

[liminzhu]

Console isn't readable from script, but one workaround I see being suggested on stackoverflow of is to override console.log to also log in places that are visible to you (e.g. write it into a file, etc.).