5
Allow interfaces to trigger item saves
Source: directus/directus#25316 · opened by @Pachat
Summary Add functionality to automatically reset form dirty state when auto-save operations (like onBlur PATCH requests) complete successfully. Cuurently • Save buttons remain enabled even after successful auto-saves • Navigation triggers unnecessary "unsaved changes" dialogs • Users are confused about whether their changes have been saved • Form state becomes inconsistent with actual data state Basic Example _No response_ Motivation • Real-time editing interfaces - Rich text editors, code editors, or other complex inputs that benefit from auto-save • Form optimization - Reducing user friction by eliminating unnecessary save prompts • Mobile-friendly forms - Better experience on touch devices where blur events are common • Collaborative editing - Supporting real-time collaboration features without confusing form states Detailed Design Implement automatic form dirty state management that: 1. Detects succe…
No pledges yet. Be the first to back this.
Comments
Similar requests
In flows, why {{$trigger.keys}} for the key on action create, and {{$trigger.keys[0]}} on action update
1 vote · 0 comments
Notification when multiple persons are working in 1 item
51 votes · 0 comments
Trigger manual flow directly in the "Settings" Flow Design page
6 votes · 0 comments
Add Simple Link to Triggered/Triggering Flow
2 votes · 0 comments
Show Count of Selected Items on Display Page
1 vote · 0 comments
No comments yet.