React 19.3 gives us useful new tools for making interfaces feel connected and working with groups of DOM elements. The question is where to spend your learning time. Start with one interaction you can understand, build, and test, then reach for the next API when it solves a problem you actually have.
The React team released 19.3 on 9 September 2026, making View Transitions and Fragment refs stable. This issue suggests a learning order rather than a complete changelog. You can explore the full set of changes in the official React 19.3 announcement.
Learn View Transitions through one small interaction
Imagine a product card that expands to reveal more information. The content should change correctly first. Then an animation can help the reader follow what moved or appeared.
React's <ViewTransition> component lets you put an animation boundary around that UI. It works with qualifying updates such as Transitions and Suspense reveals. Wrapping a component alone does not make every ordinary state update animate.
For a first experiment, put the details area inside <ViewTransition> and mark its visibility update with startTransition. Both are imported from React. Follow the ViewTransition reference and interactive examples for boundary placement.
Keep the two ideas separate in your head: startTransition marks a non-blocking React update; <ViewTransition> coordinates the visual change. startTransition itself is not new in 19.3. It also does not give you a pending flag; useTransition provides that. Keep controlled text-input updates outside Transitions. The startTransition documentation explains these limits.
Make motion useful, then make it optional
Choose a place where motion explains a relationship: opening details, switching between related views, or reordering a list. Check that the interface remains understandable when the animation is absent.
Let React coordinate each change; avoid also calling document.startViewTransition for it. This API currently targets React DOM. Check your browsers and framework integration in the ViewTransition API notes.
Reduced-motion support needs deliberate attention. React does not automatically disable these animations for that preference. Add an appropriate prefers-reduced-motion rule and verify the result with the setting enabled. MDN explains how the reduced-motion media feature works.
Learn Fragment refs when a wrapper gets in the way
A Fragment groups siblings without adding a DOM wrapper. In 19.3, an explicit <Fragment> can also receive a ref. That ref gives you a FragmentInstance with supported operations across the group's DOM children, rather than a new wrapper element.
A useful exercise is a pair of sibling form fields with a button that focuses the first available input. A Fragment ref can provide that group-level focus behavior without inserting an extra <div> solely to hold a ref.
Use the explicit Fragment component imported from React. The shorthand <>...</> syntax cannot accept a ref. Also distinguish the methods: focus can search nested children, while group event listeners and observers operate on first-level DOM children. Read the Fragment reference and focus examples before treating the ref like a single HTMLElement.
Keep semantic HTML where it has a purpose. A Fragment does not replace a fieldset, list, or other element that communicates structure to the browser and assistive technology.
Know what else exists, without learning it all today
- Browser-dependent rendering: use(browser()), with browser imported from react-dom, can defer a Client Component's server rendering to a surrounding Suspense fallback. Keep it for UI that genuinely needs the browser. It needs a Suspense boundary and is not a general reason to remove useful server-rendered content. See the browser API reference.
- Trusted Types: React DOM now preserves trusted objects when passing them to relevant browser APIs. You still need appropriate sanitization policies; the integration does not make arbitrary HTML safe.
- Server Components and Context: a Server Component can render an imported client Context directly, removing a wrapper that only forwards its value. This does not mean Server Components can create or read client Context.
The React 19.3 release notes explain the last two changes. Learn them when your application needs them.
Your next practice session
Use a small project with React 19.3 and a matching react-dom version. Check your framework, type definitions, and any coding sandbox's installed dependencies before trying the new exports.
- Build an expandable card with correct state and keyboard-operable controls.
- Add one ViewTransition boundary and mark its visibility update as a Transition.
- Test rapid repeated clicks, reduced motion, and behavior without a visible animation.
- In a separate example, group two sibling fields with an explicit Fragment ref and focus the first input from a button.
- Explain why you chose each API, what the ref actually refers to, and what should still work if the animation never runs.
That is a useful first pass through 19.3: understand one visible interaction, solve one concrete DOM problem, and keep the official references close when you need more detail.