Mislabeled Button, Close is really Abort!
Bug #156981 reported by
Stephen Gornick
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnomebaker (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: gnomebaker
Gnomebaker displays a dialog titled "Baking" which displays the status of the Burn, along with a button labeled "Close".
However pressing the Close button does not cause a confirmation dialog and immediately closes the window. This also effectively aborts the burn operation.
Other applications can be "closed" but they still run (e.g., Amarok, Pidgin IM, etc.) so the end-result of this "close" button might be confusing to some.
Should not the close button first prompt the user to verify close (and terminate any baking that might be in progress)? Or if not, then perhaps the button would be best labeled "Abort"?
| description: | updated |
| Changed in gnomebaker: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Jerome (jerome-jolimont) wrote | #1 |
| Changed in gnomebaker: | |
| status: | New → Confirmed |
To post a comment you must log in.
I confirm the bug.
-> Button label should be "Cancel".
-> Confirmation should be asked.