You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a non-standard 'Text Size' in Windows 11, the ondragend event's ClientX and ClientY coordinates are not correctly being scaled when the RasterizationScale is manually set.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
136.0.3240.76
SDK Version
1.0.3240.44
Framework
Winforms
Operating System
Windows 11
OS Version
10.0.26100 Build 26100
Repro steps
To change the Windows 'text size' value, go to Settings > Accessibility > Text Size.
Uh oh!
There was an error while loading. Please reload this page.
What happened?
When using a non-standard 'Text Size' in Windows 11, the
ondragend
event's ClientX and ClientY coordinates are not correctly being scaled when the RasterizationScale is manually set.Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
136.0.3240.76
SDK Version
1.0.3240.44
Framework
Winforms
Operating System
Windows 11
OS Version
10.0.26100 Build 26100
Repro steps
To change the Windows 'text size' value, go to Settings > Accessibility > Text Size.
To run the demo:
To reproduce the issue, perform the following steps multiple times with different Windows' 'Text Size' values. (100% and maximum are recommended):
ondragend
ClientX/ClientY coordinates will appear on screenonclick
event ClientX/ClientY coordinates will appear on screen.At 100%, the
ondragend
values are correct (approximately 800x600 when releasing over the target emoji) and will match theonclick
event.At higher text scaling values, the
ondragend
values are incorrect and do not match theonclick
event.Repros in Edge Browser
No, issue does not reproduce 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: