We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When clicking on the area where “Tab Ctrl” and “WebView2” overlap, the dialog box UI stops.
The issue is reproduced with more than one parent. (Main Dialog -> Child Dialog -> WebView2)
There is no problem with having only one parent. (Main Dialog -> WebView2)
Same problem as in the link below. #3433
Blocking. My app's basic functions are not working due to this issue.
Stable release (WebView2 Runtime)
124.0.2478.80
1.0.2478.35
Win32
Windows 11
22631.3527
I've added a sample project that reproduces the issue. WebView2BugReport.zip
Below is a capture of the sample project. Clicking on the red overlap area stops the dialog.
Yes, issue can be reproduced in the corresponding Edge version
No, this never worked
No response
The text was updated successfully, but these errors were encountered:
bradp0721
No branches or pull requests
What happened?
When clicking on the area where “Tab Ctrl” and “WebView2” overlap, the dialog box UI stops.
The issue is reproduced with more than one parent.
(Main Dialog -> Child Dialog -> WebView2)
There is no problem with having only one parent.
(Main Dialog -> WebView2)
Same problem as in the link below.
#3433
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
124.0.2478.80
SDK Version
1.0.2478.35
Framework
Win32
Operating System
Windows 11
OS Version
22631.3527
Repro steps
I've added a sample project that reproduces the issue.
WebView2BugReport.zip
Below is a capture of the sample project.
Clicking on the red overlap area stops the dialog.
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: