microsoft / microsoft/react-native-windows
KeyDown Event is getting triggered for every character entered in TextInput
Open
@vineethkuttan is already working on this.
Since Jul 24, 2025.
Area: Fabric
Area: TextInput
bug
New Architecture
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
For PR #14946 , during implementation of onScroll , we couldn't emit the event , when up arrow or down arrow button is pressed.
Cause on every text pressed the onKeyDown event is getting triggered. Because of this , we couldn't emit onScroll event for keyup and keydown
Steps To Reproduce
i) Debug the RNW
ii)Set the debug point to onKeyDown function in windowsTextInput and open textInput and type something.
Expected Results
No response
CLI version
17.0.0
Environment
System:
OS: Windows 11 10.0.26100
CPU: "(16) x64 AMD EPYC 7763 64-Core Processor "
Memory: 37.41 GB / 63.95 GB
Binaries:
Node:
version: 22.17.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.22
path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm:
version: 10.9.2
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
Versions:
- 10.0.19041.0
- 10.0.22621.0
- 10.0.26100.0
IDEs:
Android Studio: Not Found
Visual Studio:
- 17.14.36301.6 (Visual Studio Enterprise 2022)
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react: Not Found
react-native: Not Found
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Community Modules
No response
Target React Native Architecture
None
Target Platform Version
None
Visual Studio Version
None
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.