MicrosoftEdge / MicrosoftEdge/WebView2Feedback
IFrame navigation fail when running under low IL
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Associated with https://github.com/MicrosoftEdge/WebView2Feedback/issues/198.
I'm experiencing problems with IFrame elements when attempting to use the WebView2 component from a security sandboxed application running under low integrity level (low IL).
Steps to reproduce:
- Build WebView2APISample from https://github.com/MicrosoftEdge/WebView2Samples in debug x64 (tested at latest 0b7797b3ce0646160a0edff0075bb471498b2b0c commit at master)
- Run
icacls WebView2APISample.exe /setintegritylevel Lowso that it will run in low IL. - Run
WebView2APISample.exe --userdirectoryfolder=%LOCALAPPDATA%Low\Temp - Navigate to
https://www.w3schools.com/tags/tag_iframe.ASP - Press "Try it Yourself" button
- Observe that new window opens and the following error dialog is shown multiple times:
Navigation Failure
---------------------------
IFrame navigation failed: COREWEBVIEW2_WEB_ERROR_STATUS_CONNECTION_ABORTED

Process Explorer can be used to check if a process runs under the low, medium or high IL.
Version
SDK: Microsoft.Web.WebView2 1.0.1056-prerelease
Runtime: Microsoft Edge WebView2 Runtime 96.0.1054.34
Framework: WebView2APISample sample project (build using VS2019)
OS: Windows 10 19043.1348 (x64)
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 by reproducing the failure in the WebView2APISample project using the low-integrity icacls command, the specified user directory, and the w3schools iframe page. Compare the observed navigation error with the linked WebView2Feedback issue; done would require resolving or clearly identifying the cause of iframe navigation failure under low IL.
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