We’re excited to release React Native Windows 0.84.0, aligned with React Native 0.84.1. React Native Windows v0.84 delivers input-handling improvements such as standard click events and imperative focus, theme-aware defaults and robust hit-testing semantics.<\/p>\n
Visual Studio 2026 is required for 0.84 version of RNW. onClick<\/strong>\u00a0and\u00a0 Fabric components now fire standard\u00a0 Imperative Focus via\u00a0 The imperative\u00a0 Theme-Aware Default Text Color<\/strong><\/p>\n Default text color now automatically adapts to the system’s light or dark mode setting. Windows developers no longer need to manually handle theme changes for default text \u2014 apps will look correct out of the box whether the user is in light mode, dark mode, or switches between them at runtime.<\/p>\n Keyboard-Only Focus Visuals<\/strong><\/p>\n Focus visuals are now shown only when navigating via keyboard, matching standard Windows platform behavior. This eliminates distracting focus rectangles during pointer interactions while preserving clear focus indicators for keyboard and accessibility users.<\/p>\n Stricter Hit-Testing for\u00a0 Native Performance Benchmarking Infrastructure<\/strong><\/p>\n A new native performance benchmarking infrastructure measures the full Fabric rendering pipeline \u2014 from JS reconciliation through Fabric and Yoga layout to Composition commit and frame presentation \u2014 for all core components. Windows developers can now profile rendering performance at the native level, catch regressions in CI, and make data-driven optimization decisions.<\/p>\n RNW v0.84 includes targeted fixes for build tooling and CI reliability:<\/p>\n With RNW v0.84, input-handling parity takes a significant step forward. The addition of\u00a0 If you encounter missing properties or functionality, please\u00a0open an issue<\/a>. Comments on existing issues help us prioritize what to tackle next.<\/p>\n \ud83d\udd17 For a full list of known gaps, see:\u00a0Missing Properties \u00b7 React Native for Windows<\/a><\/p>\n Install the latest\u00a0React Native Gallery (0.84)<\/strong>\u00a0to explore the new features and component improvements in action.<\/p>\n Search “React Native Gallery” in the Microsoft Store or use the\u00a0direct link<\/a>. The Gallery app is the fastest way to see how each component looks and behaves on Windows and is a great reference when building or migrating your own apps.<\/p>\n If you’re interested in getting started with React Native for Windows, check out our website at\u00a0aka.ms\/reactnative<\/a>.<\/p>\nMinimum Requirements<\/code><\/strong><\/p>\n<\/code><\/p>\nonAuxClick<\/code>\u00a0Events for Fabric Components<\/strong><\/p>\nonClick<\/code>\u00a0and\u00a0onAuxClick<\/code>\u00a0events, bringing RNW’s click-handling model in line with the W3C specification. Windows developers can now handle primary and auxiliary (middle-click) interactions using the same patterns as web and other React Native platforms \u2014 enabling consistent context menus, open-in-new-tab gestures, and multi-button input without custom workarounds.<\/p>\nview.focus()<\/code><\/strong><\/p>\nfocus()<\/code>\u00a0API is now enabled for Fabric views. Windows developers can programmatically move focus to any component \u2014 unlocking guided flows, accessibility enhancements, and keyboard-driven navigation patterns that previously required native workarounds.<\/p>\noverflow: hidden<\/code><\/strong><\/p>\noverflow: hidden<\/code>\u00a0now correctly prevents hit-testing on clipped content. Previously, elements visually clipped by their parent could still receive touch and pointer events. Windows developers now get predictable input behavior \u2014 if content is clipped, it can’t be interacted with \u2014 matching expectations from web and other React Native platforms.<\/p>\n\ud83d\udd27 Reliability & Stability<\/h3>\n
\n
onClick<\/code>\u00a0\/\u00a0onAuxClick<\/code>\u00a0events added<\/strong>\u00a0\u2014 Components now fire these events. If your code previously relied on the absence of these events, you may need to update handlers.<\/li>\nm_childrenContainer<\/code><\/strong>\u00a0\u2014 Custom components using a custom visual to mount children will no longer see an intermediate container. This improves rendering but may affect components that relied on the previous container structure.<\/li>\nfocus()<\/code>\u00a0enabled<\/strong>\u00a0\u2014\u00a0view.focus()<\/code>\u00a0now works in Fabric. Existing code calling\u00a0focus()<\/code>\u00a0that previously had no effect will now move focus.<\/li>\n<\/ul>\n\ud83d\udcca Feature Parity Progress<\/h3>\n
onClick<\/code>,\u00a0onAuxClick<\/code>, imperative\u00a0focus()<\/code>, and corrected hit-testing for\u00a0overflow: hidden<\/code>\u00a0closes several long-standing gaps between RNW and web\/mobile platforms.<\/p>\n\ud83c\udfc1 Gallery App Updates<\/h3>\n
\ud83d\udce6 Release Details<\/h3>\n
\n
\ud83d\udd17 Reference Links<\/h3>\n