MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Intermittently, WebView2 controls are not rendered, and the window behind the dialog with the control is visible through the window.

Open
#4,302 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

image

The page loads successfully and the DOM tree is normal, but the rendered screen is not visible.

An issue occurs intermittently, and when the problem occurs, the screen does not appear the same until the management process of msedgewebview2 is restarted.

Setting --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds did not help solve the problem.

Additionally, when an issue occurs, the web page content is displayed normally in the 3D view of developer tools.

The GPU information file of the PC where the problem occurs is also attached.
about-gpu-2024-01-11T07-54-48-889Z.txt

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

120.0.2210.121

SDK Version

1.0.1518.46

Framework

Win32

Operating System

Windows 11

OS Version

11.0.22621

Repro steps

Opens a dialog where a WebView2 control is created, and when a WebView2 control is created, displays the desired page using Navigate.

Repros in Edge Browser

No

Regression

Don't know

Last working version (if regression)

No response

AB#48765155

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

Start with the dialog repro where a WebView2 control is created and navigated to the desired page. Reproduce the intermittent invisible-rendering state on Windows 11 using the reported runtime and SDK versions, then compare the visible window with the page shown in developer tools. Done means the rendering failure is reproducible and its cause or a verified fix is documented.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.