React Daily: Fragment Instances Get Shadow DOM and Document Position Fixes
Two related fixes from developer BlackHatMan address Fragment Instance behavior at DOM boundaries—one correcting compare document position results at the root container, the other fixing blur behavior inside shadow roots. Both trace back to how fragment instances interact with the boundary between React's tree and the native DOM.
Duration: PT2M16S
Episode overview
This episode is a short developer briefing from React Daily.
It explains recent repository work in plain language.
- Show: React Daily
- Published: 2026-09-13T06:00:33Z
- Audio duration: PT2M16S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's September 13th, and today's activity centers on one theme: Fragment Instances behaving correctly at the edges of the DOM.
Two pull requests from BlackHatMan tackle related bugs in how Fragment Instances interact with native browser APIs. In PR 37613, compare document position was returning an implementation-specific result instead of correctly reporting contains or preceding relationships—specifically for the root container passed to…
PR 37615 fixes a related edge case: fragment blur inside a shadow root. The original implementation looked for the focused element through document dot active element, but inside a shadow tree, focus retargets to the shadow host—which is never a child of the fragment. So the traversal never matched, and blur…
Together these two PRs point to the same underlying theme: Fragment Instance methods were written with assumptions about a flat document tree, and both root containers and shadow roots break those assumptions in different ways. If you're working with fragment refs, expect increased robustness here, particularly if…
Separately, two PRs from DavidKhasoa, both titled simply "Dev," touched the README. No further detail was provided,…
W…