MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Bug] WPF null BoundingRectangle property

Open
#4,118 1 comment 0 reactions 1 assignee View on GitHub

@jennifer-nejad is already working on this.

Since Nov 2, 2023.

bug tracked
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
  1. Downloaded the Main branch of the WebView2 Samples and load the WebView2WpfBrowser solution.
  2. Compile the sample
  3. Run the application
  4. Download the Accessibility Insights tool
  5. Within the Accessibility Insights tool select the "Inspect" menu item.
  6. Change the "What to select" drop down to "Entire app"
  7. Switch to the WPF sample app
  8. Select the "Test" icon in the top right portion of the app
  9. Notice the errors within the Accessibility Insights tool
Regression

Don't know

Last working version (if regression)

No response

AB#48487699

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.