MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: widget using IWidgetResourceProvider to display web-content render blank

Open
#5,069 1 comment 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?

Our team project is attempting to use web-content to display a webpage on the widget dashboard. However, it is rendering as a blank page.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

1.0.2957.106

SDK Version

1.6.250108002

Framework

WinUI3/WinAppSDK

Operating System

Windows 11

OS Version

No response

Repro steps

Follow this official tutorial
https://learn.microsoft.com/en-us/windows/apps/develop/widgets/web-widget-providers

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

Start with the official web-content widget provider tutorial and reproduce the blank page on Windows 11 using WebView2 Runtime 1.0.2957.106, SDK 1.6.250108002, and WinUI3/WinAppSDK. Compare the widget behavior with the corresponding Edge version and document a confirmed cause or actionable fix once the web content renders.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.