MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Bug] WPF null BoundingRectangle property
@jennifer-nejad is already working on this.
Since Nov 2, 2023.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
We have a WPF application that contains a WebView2 control hosting web content. When our automation team runs the Accessibility Insights tool against our app the WPF View hosting the WebView2 control displays 6 errors stating "An on-screen element must not have a null BoundingRectangle property". When I looked at the Visual Tree I noticed the errors were coming from within the WebView2 control itself.
So to test the problem in isolation I downloaded the Main branch of the WebView2 Samples and loaded up the WPF sample. When I run the Accessibility Insights tool against the sample app I receive the same 6 null BoundingRectangle property errors.
I have included the Accessibility Insights test results.
TestResults 11-01-23.zip
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
118.0.2088.76
SDK Version
1.0.2164-prerelease
Framework
WPF
Operating System
Windows 10
OS Version
19045.3570
Repro steps
- Downloaded the Main branch of the WebView2 Samples and load the WebView2WpfBrowser solution.
- Compile the sample
- Run the application
- Download the Accessibility Insights tool
- Within the Accessibility Insights tool select the "Inspect" menu item.
- Change the "What to select" drop down to "Entire app"
- Switch to the WPF sample app
- Select the "Test" icon in the top right portion of the app
- Notice the errors within the Accessibility Insights tool
Regression
Don't know
Last working version (if regression)
No response
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.
Assessment
This issue has not been assessed yet.