Don't warn about unsaved changes for an empty file
Bug #889371 reported by
Danielle Foré
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Scratch |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If I create a document, type some stuff, then erase all of it I will still receive an "unsaved changes" dialog.
Changed in scratch: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 1.1 |
Changed in scratch: | |
status: | Confirmed → Fix Committed |
Changed in scratch: | |
status: | Fix Committed → Fix Released |
milestone: | luna-beta1 → 1.1 |
To post a comment you must log in.
I think we need to think about this. It's "better to get an obnoxious warning than losing work". Sometimes we may delete all text and then close Scratch by accident.
All text editors I tried ask you to save/quit with blank files.