MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Additional Debugging Support for Injected Scripts
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AddScriptToExecuteOnDocumentCreated and ExecuteScript APIs described in the issue, along with the linked work item and existing discussion. Done should mean injected scripts are listed in the Source tab and support setting breakpoints for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100