The Verifiable Credentials Working Group has published a First Public Working Draft today for the Verifiable Credential Forgery Defense v1.0 specification. This publication is complementary to the publication of quantum-resistant cryptosuites and is motivated by the same threat. While cryptosuites let issuers secure new proofs with post-quantum signatures, this specification lets an issuer establish post-quantum-backed authenticity for credentials that may have been signed with conventional quantum-vulnerable algorithms and cannot, or is not feasible, to re-issue them. This is achieved by publishing a witness list that is itself the subject of a separate Verifiable Credential that can be signed with a quantum-resistant scheme.
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen. For compatibility with existing mouse-based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
Following the newer Recommendation, Pointer Events Level 2 has been marked as a W3C Superseded Recommendation:
1198. This week, we look at how to answer the question every author dreads: "So, what's your book about?" with workplace communications coach Joel Schwartzberg. We look at the difference between describing a book and selling it, how nonfiction authors can craft point-driven responses, and how fiction writers can distill their stories into a compelling pitch.
Joel Schwartzberg is a workplace communications coach, speaker, and speechwriter. He's the author of "Get to the Point: Simplify, Sharpen, and Sell Your Message," and you can find him at joelschwartzberg.net
Snapshot Tests are an uncommon type of test that focuses on checking that no regressions were introduced after a code refactoring. Let’s learn how they work and how to use the Verify NuGet library to add them to your test suite.
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.
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.
It’s not surprising that Microsoft is looking to turn its Copilot platform into a “Super App,” given that its rivals are doing the same. But Microsoft is going about the task in a way that doesn’t follow its usual playbook, by putting a big bet on a consumer-savvy hire from the outside with some feather-ruffling ways.
The company’s newly minted Copilot Executive Vice President Jacob Andreou came to Microsoft from Greylock Partners and before that, Snapchat-maker Snap. Andreou currently oversees more than 11,000 Microsoft employees, according to a recent profile in Fortune.
Microsoft is bringing onboard another former Snap (and Discord) vice president, Peter Sellis, to help, GeekWire has learned. Sources say Sellis will be leading Copilot Design, Growth and Engineering, reporting to Andreou.
Andreou is part of a recently formed Copilot Leadership Team. His charter is to lead the “Copilot experience” by driving design, product, growth and engineering, as outlined in a March 2026 reorg memo from CEO Satya Nadella. He is one of a small group charged with shaping the future of Copilot, alongside others focused on the underlying Copilot platform and AI models.
Given Andreouâs Snap background, his plan to meld Microsoft’s consumer and enterprise Copilot experiences makes sense. It wonât be a snap, however. (See what I did there?)
Even though both share the Copilot brand, consumer Copilot and Microsoft 365 Copilot don’t work the same way or use the same data sources or architecture. To boot, Microsoft hasn’t had a lot of luck with this kind of consumer-enterprise unification, as evidenced by the low interest in and uptake of its free, consumer-focused Teams product compared to its business-focused Teams collaboration offering.
The 33-year-old, Los Angeles-based Andreou seemingly is undaunted by the challenge and is pushing some employees to clock 12-hour days to keep up with younger, AI-focused companies, Fortune reports.
Microsoft was infamous for requiring employees to work long hours and weekends during crunch times leading up to delivering Windows NT and Windows 95, but not so much in recent years. Microsoft is known as a place where outsiders often struggle to thrive compared to those who climb the corporate ladder for years, making Andreouâs approach feel even riskier.
Andreou has been a big backer of the Tasks productivity layer in consumer Copilot, which is still in public preview. Tasks, which enables Copilot to handle actionable items, is similar to the recently released Copilot Cowork layer that is part of Microsoft 365 Copilot. (I asked Microsoft if the two would merge as a single Cowork-type offering at some point but was told the company had no comment.)
However, the holy grail remains the “Super App.” With the Copilot Super App, Microsoft is looking to give consumers and business users a reason to stay within Copilot regardless of the AI task with which they â or their agents â are engaging.
“Come summer, we will be bringing coding to all knowledge work within one Copilot Super App. That’s really exciting. So you’re going to have Chat, Cowork, and Code all in Copilot,” Nadella told Microsoft Build conference attendees in early June.
Microsoft isn’t the only AI-focused company working on extending its AI coding capability beyond just developers. Nor is it the only one betting on the Super App concept.
OpenAI is working to turn ChatGPT into a Super App that brings together ChatGPT and Codex into a single environment that operates like a personal assistant.
Anthropic is extending Claude to become a Super App (though it hasn’t used that terminology), as well, by creating a single environment that combines productivity, development and automation tools.
The Copilot Super App isnât Andreouâs only focus. He tells Fortune that AI model choice and home-grown AI model excellence also are among his key priorities.
Microsoft is expanding model choice in the Copilot Cowork feature beyond Anthropic to include OpenAI and soon, Microsoftâs own Cowork 1 model â which may be based on Microsoftâs hosted version of the open-source DeepSeek model. Cowork 1 will be the newest addition to Microsoftâs growing pool of Microsoft-developed models, seven of which debuted at Build this year. Microsoft is seeking to position itself as the champion of lower cost, efficient models built for those who are token-maxxed out.
Andreou definitely has his work cut out for him as a consumer guy in a heavily enterprise-centric company.
Microsoft 365 Copilot and consumer Copilot are just two of more than two dozen different âCopilotâ-branded commercial offerings available across the various Microsoft product teams, which can feel overwhelming.
Microsoft also needs to give users a clearer way to find and use the quickly expanding stable of first- and third-party agents, like the OpenClaw-based Microsoft Scout personal assistant. Will Andreou and his Super App quest bring at least some order to the Copilot and agent madness? Weâll know more sometime this summer.
Log in
What’s New in RNW v0.84?
Reliability & Stability
Feature Parity Progress
For a full list of known gaps, see:Â 
Gallery App Updates
Release Details
