MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: RasterizationScale does not correctly scale ondragend coordinates with Text Size

Open
#5,249 0 comments 2 reactions 1 assignee View on GitHub

@Navdeep-ss is already working on this.

Since May 23, 2025.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

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):

  • Drag the frog emoji (🐸) to the target emoji (🎯) and release the left mouse button
  • The ondragend ClientX/ClientY coordinates will appear on screen
  • Click the target emoji
  • The onclick 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 the onclick event.

At higher text scaling values, the ondragend values are incorrect and do not match the onclick 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

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.