MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Is it possible to configure the length of time of what WebView2 considers a CoreWebView2ProcessFailedReason.Unresponsive event?

Open
#1,749 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request priority-low tracked
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.

Yes. I'm currently working with a script that takes several seconds to finish. However, the time to run is normal and expected, but the component detects is as “unresponsive” and raises the event.

Describe the solution you'd like and alternatives you've considered

I know this is a rare scenario, but if the timeout was an option like in, say, CoreWebView2Settings.UnresponsiveTimeout, it would work for cases like this where we already know a script will take a long time to run.

AB#36391589

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the WebView2 API surface and the linked AB#36391589 work item to understand whether the unresponsive-event timeout is configurable. Confirm the expected behavior for long-running scripts and document what API change and validation would constitute completion.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.