MicrosoftEdge / MicrosoftEdge/WebView2Feedback
EnsureCoreWebView2Async not completing, and SetVirtualHostNameMapping not working until WV2 instance is visible
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
EnsureCoreWebView2Async not completing, and SetVirtualHostNameMapping not working until WV2 instance is visible. Details at https://weblog.west-wind.com/posts/2022/Jul/14/Fighting-WebView2-Visibility-on-Initialization
Version
SDK: TBD
Runtime: ~103
Framework: WPF
OS: Irrelevant
Repro Steps
See post above.
Screenshots
See post above.
Additional context
See post above.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked weblog post and the issue's WPF reproduction steps, using the reported ~103 runtime context. Confirm the behavior around EnsureCoreWebView2Async and SetVirtualHostNameMapping before the WebView2 instance is visible; done means the cause and a reproducible resolution are documented.
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