MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Navigate to a normal web page but trigger a file download callback

Open
#4,417 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?

This problem occurs occasionally. Our client frequently loads a normal web page link, but sometimes it fails to load the web page and returns the error code: COREWEBVIEW2_WEB_ERROR_STATUS_CONNECTION_ABORTED

After careful analysis of the log, we found that loading this normal web page eventually triggered file download, and the API call sequence is as follows:

  Navigate(url)
  OnNavigationStarting(url)
  OnWebResourceRequested(url)
  OnNavigationCompleted(url)  //get error code  **COREWEBVIEW2_WEB_ERROR_STATUS_CONNECTION_ABORTED**
  OnDownloadStarting(url)   //Triggered to start downloading
Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

122.0.2365.80

SDK Version

1.0221

Framework

Win32

Operating System

Windows 10, Windows 11

OS Version

No response

Repro steps

Load a URL normally

Repros in Edge Browser

Yes, issue can be reproduced 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

No repository file or test is named. Start by reproducing the reported Navigate, navigation event, and download event sequence with the stated WebView2 and Edge versions on Windows. Done means identifying why a normal page triggers the download callback and documenting a reliable reproduction and expected behavior.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.