Skip to content

[Frontend] settings-content.tsx does not confirm before discarding unsaved changes on navigation #1086

Description

@grantfox-oss

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

  • Track dirty state in the settings form
  • Show a confirmation prompt (native beforeunload for tab close, and an in-app confirm for internal navigation) when there are unsaved changes
  • Add a test covering the dirty-state detection logic

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

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26Stellar WaveIssues in the Stellar wave programenhancementNew feature or requestfrontendFrontend related tasks

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions