The Wire · Showcase
REACT HARDENS FLIGHT CLIENT AGAINST UNTRUSTED INPUT, FRAGMENT BLUR BUG FIXED
By RepoJournal · Filed · About Meta
React added traversal guards to Flight Client to defend against prototype pollution attacks, while a separate fix ensures Fragment refs properly blur nested focused elements.
React's Flight layer got defense-in-depth coverage [1] with guards ported from ReplyServer to FlightClient, protecting against catastrophic vulnerabilities if untrusted input reaches the serialization layer. In parallel, a Fragment DOM bug [2] landed that fixes a regression where blur() would miss focused elements nested inside Fragment host children, treating nested active elements as part of the Fragment scope. On the React Native side, the team is rolling out the Android pull model for real with wiring complete behind a feature flag [3], making the commit thread signal transaction availability while the UI thread pulls and applies at mount time, matching iOS/macOS behavior. The changes are byte-for-byte identical when the flag is off (default), and include Robolectric test coverage [4] validating the notification path. Maestro test isolation landed [5] to retry only failing iOS flows in isolated processes, preventing transient driver failures from restarting the full suite. Flow config got modernized [6] to use the new glob ignore system, and a new feature flag [7] gates transparent tint color handling on Images.
One email a day. Unsubscribe in one click.
Keep up with Meta in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review Flight Client changes for your serialization pipeline, particularly if handling any external input facebook/react [plan]
- → Test Fragment blur behavior in your app if using Fragment refs with nested focus management facebook/react [monitor]
- → Monitor enableMountingCoordinatorPullModelAndroid flag rollout on Android for pull model adoption facebook/react-native [monitor]
References
- [1] [Flight] Port ReplyServer traversal guards to FlightClient ↗ facebook/react
- [2] [DOM] Blur focused descendants in Fragment refs ↗ facebook/react
- [3] Wire the Android pull model in C++ behind the feature flag (#57579) facebook/react-native
- [4] Add JVM tests for the Android pull model plumbing (#57583) facebook/react-native
- [5] Make Maestro iOS retries flow-specific (#57749) facebook/react-native
- [6] Switch to the new glob system of ignore in react-native flowconfig (#57758) facebook/react-native
- [7] Add enableImageTransparentTintColor feature flag (#57607) facebook/react-native