Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
frontend/src/app/settings/settings-content.tsx lets users edit preferences, but if a user navigates away (via Navbar link or back button) mid-edit with unsaved changes, those edits are silently lost with no warning. This is a common UX gap for settings/preference forms.
Acceptance criteria
Files to touch
frontend/src/app/settings/settings-content.tsx
Out of scope
- Auto-saving settings
- Building a generic unsaved-changes framework for all forms
Why this matters
frontend/src/app/settings/settings-content.tsxlets users edit preferences, but if a user navigates away (via Navbar link or back button) mid-edit with unsaved changes, those edits are silently lost with no warning. This is a common UX gap for settings/preference forms.Acceptance criteria
beforeunloadfor tab close, and an in-app confirm for internal navigation) when there are unsaved changesFiles to touch
frontend/src/app/settings/settings-content.tsxOut of scope