MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: CustomScheme after TrySuspend, TrySuspendCompleted can't trigger

Open
#4,851 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

When calling CreateWebViewEnvironment with Options Internal, 'gztime' is defined through CustomsSchemeRegistration. Then, the web page of this protocol is loaded in the webview, and the WebResourceRequested callback is processed to load normally. Then, the TrySuspend function is called on the page, but TrySuspendCompleted cannot be triggered. Loading HTTP URL can be triggered

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

129.0.2792.79

SDK Version

1.0.2792.79

Framework

Win32

Operating System

Windows 10

OS Version

19045.4894

Repro steps

step:

  1. calling CreateWebViewEnvironment with Options Internal, 'gztime' is defined through CustomsSchemeRegistration.
  2. the web page of gztime://index is loaded in the webview, and the WebResourceRequested callback is processed to load normally.
  3. TrySuspend function is called on the page
  4. TrySuspendCompleted cannot be triggered.
    excepted:
    TrySuspendCompleted trigger
Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

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

Reproduce the issue using CreateWebViewEnvironment with Internal options, CustomSchemeRegistration for gztime, and the WebResourceRequested callback. Start by comparing the custom-scheme flow with the HTTP URL flow around TrySuspend and TrySuspendCompleted. Done means TrySuspendCompleted is triggered after suspending the custom-scheme page.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.