Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Non-standard unsaved file dialog

Open Beginner friendly
  • Is something wrong?
#1,659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
design, mobile

Research direction

Start by locating the unsaved changes confirmation dialog used when leaving an edited text file; the issue does not name a file or test. Compare its current actions with the requested Cancel, Discard, and Save and exit choices, then verify each action closes, discards, or saves and exits as described.

Written by the indexing model from the issue text.

Description

Screenshot_20261019_065020_Material Files.png

Confusing and Not As Usual Unsaved Exit Confirmation Dialog

When you are about to leave a text file that has been edit but not yet saved, you get a pop up dialog telling you so and offer according options. However, the action buttons are designed unusual unlike many editing applications which confuses lots of users

Currently
  • Cancel equals to No where it discards all edits and keep the file intact
  • Keep editing equals to Cancel which closes the dialog and abort exiting.
  • There is no Yes which saves and exit the file.
It should've been

A typical confirmation button UX design, like all editing softwares

  • Cancel / Keep Editing Closes dialog and aborts exiting
  • No / Discard Discards edit, exit and keep file intact
  • Yes / Save and exit Saves and exit
Dominant language
Kotlin
Stars
9.2k
Forks
761
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zhanghai/MaterialFiles

All issues in zhanghai/MaterialFiles

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.