GitLab Pajamas: Saving and feedback
Documents manual save versus auto-save, auto-saving changes in forms and drafts, per-input autosave timing, saving and saved feedback, undo, retry after failed autosave, leave-page warnings, and guidance to avoid autosave for sensitive financial, security, or privacy-impacting changes.
What this source can teach
Use this source to compare a documented solution with the task and states in your own product.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Autosave form | Choose autosave form when background progress preservation is safer than relying only on a final Save button. | Editing a field marks that field or section pending without clearing the user's value. | GitLab Pajamas supports autosaving form changes and drafts with per-input timing, visible saving/saved states, undo, retry, leave warnings, and sensitive-data cautions. |
| Autosave recovery | Choose autosave recovery when a background save did not complete or cannot prove that the latest value is safe. | The recovery surface appears close to the affected form, section, editor, or submit action and remains until the risk is resolved. | GitLab Pajamas supports retry after failed autosave, undo, saved feedback, leave warnings, and autosave cautions. |
| Draft state | Choose draft state when a recoverable unpublished version exists separately from a published, active, or previously saved version. | Opening a draft from a list lands in draft edit mode and preserves the unpublished values. | GitLab Pajamas supports draft save status language and clarifies when progress is saved as a draft rather than as final changed data. |
| Fake undo | Flag this anti-pattern when an Undo control does not restore the exact object, value, order, relationship, permission, selection, and visible status it claims to reverse. | The system captures reversible state before applying the action, not after users request undo. | GitLab saving and feedback guidance supports clear save, failed-save, undo, and leave-warning distinctions. |
| Unsaved changes prompt | Choose unsaved changes prompt when a user action inside the product would abandon or replace dirty local edits before they are saved. | Opening the prompt never clears the dirty values. | GitLab Pajamas documents save feedback, failed-save recovery, undo, and leave warnings for unsaved form changes. |
Comparisons supported by this source
- Autosave form vs single-page form vs multi-step form vs inline edit
GitLab Pajamas documents per-input autosave timing, status feedback, undo, retry, leave warnings, draft saving, and sensitive-data cautions.
- Autosave recovery vs autosave form vs draft state vs retry
GitLab Pajamas documents autosave failure handling, retry after failed autosave, undo, and leave warnings.
- Fake undo vs undo vs toast notification vs restore from trash vs destructive action confirmation vs autosave recovery
GitLab saving and feedback guidance supports truthful distinctions among saved, failed, undo, and leave-warning states.
- Unsaved changes prompt vs exit warning vs autosave form vs confirmation dialog
GitLab Pajamas documents save feedback, failed-save retry, undo, and leave-warning behavior for form changes.
Evidence Role
This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.
Publisher: GitLab Pajamas Design System. Last checked: .