MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Throw custom exception for WebView Control is no longer valid
@champnic is already working on this.
Since Mar 10, 2022.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
I'm seeing a lot of errors coming into my application with recent updates of the WebView control runtime. For a bit things seemed to be much better, but the problem has returned and is more persistent.
One problem is that it's not easy to detect these failures. I have the ProcessFailed handler in place, but apparently these exceptions fire before that and they are fired ALOT (presumably on any WebView operation, but I don't know because the stack trace doesn't show anything from my code).
Suggestion
One thing that would really help here if this could throw an easily trappable exception instead the generic InvalidArgumentException. Right now the only way I can do this is check if IVAE and then check the message which is not ideal. Basically when this happens I have to shut down the application. If not, there end up 100s of these errors flooding the logs in a matter of a couple of seconds before the Failed header kicks in or the app crashes (hard to tell as I've not seen it).
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.
Assessment
This issue has not been assessed yet.