[BUG]: No persistent indicator when form is processing across refresh/navigation

[vharkins1]

⚡️ Describe the Bug

When a user is filling out a form, if they refresh the page or navigate to another page on the site while the form is being processed/saved, there is no visible indicator that the form is still working. Users cannot tell whether their input is being saved or submitted and may leave thinking the action failed.

👣 Steps to Reproduce

1. Open a form rendered with FireForm.
2. Enter data into one or more fields (or trigger an autosave/long submission).
3. Refresh the browser or navigate to a different page on the site while the form is still processing.
4. Return to the form (or check the destination) and observe there is no persistent indication that the form was saving/submitting or that the operation completed.

📉 Expected Behavior

There should be a clear, persistent indicator that the form is still processing/saving even if the user refreshes or navigates away (for example: a toast/notification that persists across pages, a status bar, or a cross-page progress indicator). If the operation completes after navigation, the user should receive a confirmation (e.g., a notification or updated UI state) so they know their input was saved.

🖥️ Environment Information

• Browser: (e.g. Chrome, Firefox)
• OS: (e.g. macOS, Windows)
• FireForm version: (if known)

📸 Screenshots/Logs

N/A

🕵️ Possible Fix

• Add a persistent, cross-page save/submit indicator (toast, status bar, or site-wide notification) that remains visible across navigation/refresh until the operation completes.
• Use mechanisms like localStorage, BroadcastChannel, or a Service Worker to track in-progress operations and surface status across pages.
• Ensure autosave/submission state is persisted so users receive confirmation once processing finishes.