Skip to content
New issue

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

[Feature]: Expose RasterizationScale, ShouldDetectMonitorScaleChanges and RasterizationScaleChanged of CoreWebView2Controller in WebView2 class #4775

Open
aulati opened this issue Aug 28, 2024 · 0 comments
Labels
feature request feature request

Comments

@aulati
Copy link

aulati commented Aug 28, 2024

Describe the feature/enhancement you need

I need to disable the windows text size scaling while keep the windows dpi scaling.
After some digging I found this: #3699
However I cannot access CoreWebView2Controller in Microsoft.Web.WebView2.WinForms.WebView2, as it's a private field, ShouldDetectMonitorScaleChanges and RasterizationScaleChanged are not exposed in WebView2.

The scenario/use case where you would use this feature

I want to set ShouldDetectMonitorScaleChanges to false, then set the RasterizationScale to the value of DeviceDpi / 96, this would avoid the influence of windows text size scaling.

How important is this request to you?

Impactful. My app's user experience would be significantly compromised without it.

Suggested implementation

Expose those properties/events in Microsoft.Web.WebView2.WinForms.WebView2, or even better, _coreWebView2Controller field.

What does your app do? Is there a pending deadline for this request?

Our app use webview2 and blazor to render WinForms controls on a browser, it's now generally available internally.

@aulati aulati added the feature request feature request label Aug 28, 2024
@github-staff github-staff deleted a comment from ViniciusSCG Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request feature request
Projects
None yet
Development

No branches or pull requests

2 participants
@aulati and others