From 1f8d82ecb507522d5a3abe1b3d188dbc02518828 Mon Sep 17 00:00:00 2001
From: DS Boyce <260543580+ds-boyce@users.noreply.github.com>
Date: Thu, 25 Jun 2026 17:53:50 -0500
Subject: [PATCH] Fire onChangeDate alongside onConfirm on iOS Done

On iOS, onDateChange only fires on scroll, so an empty field confirmed
without scrolling reported a date via onConfirm while onChangeDate stayed
silent. Call onChangeDate(draft) in the Done handler for parity with Android
and web, where committing fires both together.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 src/components/forms/DateField/index.tsx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/components/forms/DateField/index.tsx b/src/components/forms/DateField/index.tsx
index 0d014fa877..3211c4d1c7 100644
--- a/src/components/forms/DateField/index.tsx
+++ b/src/components/forms/DateField/index.tsx
@@ -121,6 +121,14 @@ export function DateField({
             <Button
               label={_(msg`Done`)}
               onPress={() => {
+                /*
+                 * Commit the currently shown date even if the user never
+                 * scrolled (onDateChange only fires on scroll). This keeps
+                 * onChangeDate firing alongside onConfirm, matching Android and
+                 * web, so an empty field confirmed without scrolling does not
+                 * report a date via onConfirm while onChangeDate stays silent.
+                 */
+                onChangeDate(draft)
                 onConfirm?.(draft)
                 control.close()
               }}