Scratch

Unsaved Changes alert causes infant deaths

Bug #902678 reported by Danielle Foré
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Scratch
Fix Released
Medium
Unassigned
Scratch 1.1 "Iliad"

Bug Description

I've attached a screenshot of our dialog and gedit's dialog. I think it's safe to pretty much just copy theres and kill ours with eternal flame.

Revision history for this message
Danielle Foré (danrabbit) wrote :
Revision history for this message
Danielle Foré (danrabbit) wrote :
Revision history for this message
Cassidy James Blaede (cassidyjames) wrote :

Confirmed, babies are dying here as well.

Changed in scratch:
status: New → Confirmed
Revision history for this message
Mario Guerriero (mefrio-g) wrote :

What do you mean Cassidy?

Changed in scratch:
importance: Undecided → Wishlist
importance: Wishlist → Medium
milestone: none → 1.1
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

First, the current dialog is confusing; it states "all your work will be lost" in bold and it seems that there's nothing the user can do about this except canceling.

Second, the dialog should show up only for files that are not yet saved anywhere on the disk or saved to /tmp, following https://blueprints.launchpad.net/scratch/+spec/ditch-explicit-saving

Revision history for this message
David Gomes (davidgomes) wrote :

Cassidy, I can confirm deaths around these parts too.

Mario, he means our unsaved changes dialog is killing babies where he lives too, hence we need to change it quickly.

Mario Guerriero (mefrio-g)
Changed in scratch:
status: Confirmed → Fix Committed
Danielle Foré (danrabbit)
Changed in scratch:
milestone: luna-beta1 → 1.1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.