MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: WebView2 scrolling with Precision Touchpad is less responsive than Edge in WinUI/UWP

Open
#5,658 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

When using WebView2 hosted in a WinUI 3 or UWP application, scrolling with a Windows Precision Touchpad feels noticeably less responsive than in Microsoft Edge, even though both use the same WebView2/Edge runtime.

The issue is easy to notice on long web pages such as GitHub, Wikipedia, or other scrollable websites. Compared with Microsoft Edge, the content appears to lag slightly behind finger movement, making scrolling feel less direct and less "attached" to the touchpad gesture.

This behavior is consistent across different websites and is reproducible every time. The same pages scrolled in Microsoft Edge on the same machine feel significantly smoother and more responsive.

Expected behavior:
Scrolling in WebView2 should feel as responsive and smooth as scrolling in Microsoft Edge when using a Windows Precision Touchpad.

Actual behavior:
Scrolling in WebView2 has slightly higher perceived input latency and reduced responsiveness compared to Microsoft Edge, resulting in a less natural scrolling experience.

If this behavior is expected because of the current WinUI/UWP hosting model, could you clarify whether there are any recommended APIs or configuration options to achieve scrolling responsiveness comparable to Microsoft Edge?

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

150.0.4078.99

SDK Version

No response

Framework

WinUI3/WinAppSDK

Operating System

Windows 11

OS Version

26200.8894

Repro steps

Scroll within any WebView2 interface.

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.

Research direction

Start by reproducing the issue in a WinUI 3 or UWP WebView2 interface using a Windows Precision Touchpad, then compare the same pages in the corresponding Edge version. Check whether the WebView2 Runtime 150.0.4078.99 and the WinUI/UWP hosting model expose a relevant API or configuration; done means identifying the cause or documenting supported guidance for matching Edge responsiveness.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.