[MS] 🚀React Native Windows v0.84 is here!! - devamazonaws.blogspot.com

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.

🔥 What's New in RNW v0.84?

Minimum Requirements

Visual Studio 2026 is required for 0.84 version of RNW. onClick and onAuxClick Events for Fabric Components

Fabric components now fire standard onClick and onAuxClick events, 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 — enabling consistent context menus, open-in-new-tab gestures, and multi-button input without custom workarounds.

Imperative Focus via view.focus()

The imperative focus() API is now enabled for Fabric views. Windows developers can programmatically move focus to any component — unlocking guided flows, accessibility enhancements, and keyboard-driven navigation patterns that previously required native workarounds.

Theme-Aware Default Text Color

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 — apps will look correct out of the box whether the user is in light mode, dark mode, or switches between them at runtime.

Keyboard-Only Focus Visuals

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.

Stricter Hit-Testing for overflow: hidden

overflow: hidden now 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 — if content is clipped, it can't be interacted with — matching expectations from web and other React Native platforms.

Native Performance Benchmarking Infrastructure

A new native performance benchmarking infrastructure measures the full Fabric rendering pipeline — from JS reconciliation through Fabric and Yoga layout to Composition commit and frame presentation — 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.

🔧 Reliability & Stability

RNW v0.84 includes targeted fixes for build tooling and CI reliability:

  • NativeModule templates fixed for clang compiler — Module authors using clang to build native modules no longer encounter template compilation errors.
  • onClick / onAuxClick events added — Components now fire these events. If your code previously relied on the absence of these events, you may need to update handlers.
  • Custom visual mounting no longer creates m_childrenContainer — 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.
  • Default text color is now theme-aware — Text that previously appeared with a hardcoded color will now adapt to light/dark mode. If your app explicitly overrides text color, no change is needed; otherwise, verify appearance in both themes.
  • Focus visuals are keyboard-only — Focus rings no longer appear on pointer interactions. If your app relied on always-visible focus visuals, consider explicit styling for those cases.
  • Imperative focus() enabled — view.focus() now works in Fabric. Existing code calling focus() that previously had no effect will now move focus.

📊 Feature Parity Progress

With RNW v0.84, input-handling parity takes a significant step forward. The addition of onClick, onAuxClick, imperative focus(), and corrected hit-testing for overflow: hidden closes several long-standing gaps between RNW and web/mobile platforms.

If you encounter missing properties or functionality, please open an issue. Comments on existing issues help us prioritize what to tackle next.

🔗 For a full list of known gaps, see: Missing Properties · React Native for Windows

🏁 Gallery App Updates

Install the latest React Native Gallery (0.84) to explore the new features and component improvements in action.

Search "React Native Gallery" in the Microsoft Store or use the direct link. 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.

📦 Release Details

🔗 Reference Links

If you're interested in getting started with React Native for Windows, check out our website at aka.ms/reactnative.

You can also follow us on X @ReactNativeMSFT to keep up to date on news, feature roadmaps, and more.


Post Updated on June 30, 2026 at 10:16AM
Thanks for reading
from devamazonaws.blogspot.com

Comments

Post a Comment

Popular posts from this blog

[MS] Pulling a single item from a C++ parameter pack by its index, remarks - devamazonaws.blogspot.com

In my earlier discussion of pulling a single item from a C++ parameter pack by its index , I noted that with the Pack Indexing proposal, you would be able to write this to pull an item from a parameter pack while preserving its reference category. template<int index, typename...Args> void example(Args&&... args) { auto&& arg = (Args...[index]&&)args...[index]; using Arg = Args...[index]&&; } Why did I need to apply the (Args...[index]&&) cast ? Why can't I just write this: auto&& arg = args...[index]; or possibly decltype(auto) arg = args...[index]; Well, when you write the name of a variable, the result is an lvalue reference, even if the variable is an rvalue reference . Watch: struct S { S(S&); // construct from lvalue S(S&&); // construct from rvalue }; void whathappens(S&& s) { S t = s; // which will it use? } Try it out in your favorite compiler. This code construc...
Read more

[MS] Boosting Azure DevOps Security with GHAS Code Scanning - devamazonaws.blogspot.com

Image
Debjyoti Ganguly shares insights on the security benefits and configuration of GHAS Code Scanning with Azure DevOps. Boosting Azure DevOps Security with GHAS Code Scanning Code scanning, a pipeline-based tool available in GitHub Advanced Security, is designed to detect code vulnerabilities and bugs within the source code of ADO (Azure DevOps) repositories. Utilizing CodeQL as a static analysis tool, it performs query analysis and variant analysis. When vulnerabilities are found, it generates security alerts. CodeQL CodeQL is a powerful static analysis tool used for showing vulnerabilities and bugs in source code. It enables developers to write custom queries that analyze codebases, searching for specific patterns and potential security issues. By converting code into a database format, CodeQL allows for sophisticated, database-like queries to detect flaws. CodeQL in Action 1. Preparing the Code Create a CodeQL Database : Extract and structure the code into a database for analy...
Read more

[MS] Going beyond the empty set: Embracing the power of other empty things - devamazonaws.blogspot.com

The empty set contains nothing. This sounds really silly, but it's actually really nice. The Windows Runtime has a policy that if a method returns a collection (such as an IVector ), and the method produces no results, then it should return an empty collection, rather than a null reference . That way, consumers can just iterate over the collection without having to deal with a null test. For example, suppose you have a method Widget:: Get­Associated­Doodads which returns an IVectorView<Doodad> representing the Doodad objects that have been associated with a Widget object. If no Doodad s have been associated with the Widget , then it should return an empty vector, not a null pointer. That allows developers to write the natural-looking code: // C# foreach (var doodad in widget.GetAssociatedDoodads()) { ⟦ process each doodad ⟧ } // C++/WinRT for (auto&& doodad : widget.GetAssociatedDoodads()) { ⟦ process each doodad ⟧ } // JavaScript widget.GetAssociated...
Read more