-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
Area: ScrollViewNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricParity: WindowsRNW does not look or behave like non-RNW WindowsRNW does not look or behave like non-RNW WindowsWorkstream: Component ParityClose the parity gap between RNW and RN for core RN components and their supporting APIs.Close the parity gap between RNW and RN for core RN components and their supporting APIs.buggood first issue
Milestone
Description
Discussed in #14642
Originally posted by Ferry-200 May 6, 2025
version:
{
"dependencies": {
"react": "19.0.0",
"react-native": "0.78.0",
"react-native-windows": "^0.78.0"
}
}
I'm testing the React Native for Windows app using the new architecture (Windows App SDK). I noticed that the scroll wheel behavior is significantly different.
In the new architecture (Windows App SDK), scrolling with a mouse wheel feels much less responsive. The number of lines scrolled per wheel notch is considerably smaller compared to both the React Native Windows Gallery app and the official WinUI 3 Gallery app. As a result, scrolling through content feels sluggish and requires much more effort from the user.
This issue makes basic interaction in list views and scrollable content frustrating.
Any helps? Thanks!
5.6.mp4
Copilot
Metadata
Metadata
Assignees
Labels
Area: ScrollViewNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricParity: WindowsRNW does not look or behave like non-RNW WindowsRNW does not look or behave like non-RNW WindowsWorkstream: Component ParityClose the parity gap between RNW and RN for core RN components and their supporting APIs.Close the parity gap between RNW and RN for core RN components and their supporting APIs.buggood first issue
Activity
chrisglein commentedon May 8, 2025
Goal in the implementation was to match the numbers from WinUI, but clearly the behavior is different. Good catch. We'll look into it.
To investigate: Are there per-user mouse settings in effect here (as there are for mouse move speed)?