After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 80627 - `Are you sure you want to cancel' UI issues
`Are you sure you want to cancel' UI issues
Status: RESOLVED FIXED
Product: bug-buddy
Classification: Deprecated
Component: general
2.1.x(GNOME2.x)
Other other
: Normal minor
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks: 114848
 
 
Reported: 2002-05-02 23:06 UTC by Ben FrantzDale
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
this patch provides appropriate message for cancel UI dialog box ,with appropriate color scheme for option buttons (2.89 KB, patch)
2004-02-24 04:15 UTC, cs_is
none Details | Review

Description Ben FrantzDale 2002-05-02 23:06:09 UTC
There are several problems with the `Are you sure you want to cancel this
bug report?' dialog.

First, the green, default button does the destructive action---closing
bug-buddy.

Second, the options are `No' and `Yes' rather than something like `Close
Bug-Buddy' and `Continue bug report'

I'm not sure what the best words would be given that my suggestion here has
`close' and `continue' which could (at first glance) be taken to mean close
the popup and continue with canceling.
Comment 1 Wayne Schuller 2002-05-10 05:08:03 UTC
unfortunately I can't think of a better way to do this.

The Gnome HIG web site only has an out of date manual, so I dunno what
the gnome policy should be for this.
Comment 2 Murray Cumming 2003-06-30 13:29:34 UTC
> The Gnome HIG web site only has an out of date manual, so I dunno what
> the gnome policy should be for this.

It's not that out of date.

What's wrong with
[Close Bug-Buddy] and [Continue bug report]?
Comment 3 Bryan W Clark 2004-01-31 16:52:39 UTC
How is this handled in the new bug buddy?
Comment 4 Fernando Herrera 2004-01-31 17:05:09 UTC
Just now is:
[No]  [Yes]

Should I update to 
[Close Bug-Buddy] and [Continue bug report]?

Thanks
Comment 5 Bryan W Clark 2004-02-06 19:35:23 UTC
How about something like this:

"Informing the developers of problems is an important part of GNOME."

[Cancel bug report] and [Continue bug report]?

cc'ing usability since calum is much better at this than I am.
Comment 6 Ben FrantzDale 2004-02-06 20:03:25 UTC
That sounds good, although the "...important part of GNOME." may be a
bit odd to casual users. Perhaps something like "Developers would like
to fix this problem, but need a bug report to do so."
Comment 7 Calum Benson 2004-02-09 14:25:26 UTC
Hmm. Well, first of all I'd query whether the alert is even
necessary... having a confirmation alert pop up when you press Cancel
is uncommon and usually just annoying.  It can be warranted when data
loss might result, but in this case the worst that can happen is that
a bug goes unreported until the user stumbles across it again.

If you do want to keep the alert, things get a little ugly-- the HIG
guidelines are somewhat open to interpretation if you're confirming a
cancellation, since the button order is supposed to be (right to left)
the "action proposed by the alert" followed by the "Cancel" button...
or [Cancel]-[Cancel] in this case :)

Anyway, if we're keeping it, it could go something like (adding the
large/bold primary text, as per the HIG):

   <bold><larger>Cancel Bug Report?</larger></bold>
   Taking the time to complete this report would help
   improve the quality of the application.

                    [Complete Report] [Cancel Report]

with [Cancel Report] being the default button.  Even now I'm still not
sure those buttons are the right way around for this situation though :)
Comment 8 cs_is 2004-02-24 04:15:52 UTC
Created attachment 24709 [details] [review]
this patch provides appropriate message for cancel UI dialog box ,with appropriate color scheme for option buttons
Comment 9 Fernando Herrera 2004-02-24 09:16:30 UTC
Thanks for the patch. But now we are on string freeze and cannot add
any new string. As Calum pointed a solution is removing this dialog,
and that's what I'm going to do for 2.6 version (a minor UI change,
but it's allowed to solve an UI-reviwe bug). I will left this bug
opened and during 2.7 development we will decide if use it or not.
A side comment to your , any user visible string should be marked for
translation, using _("X") functions. Also buttons should have
accelerators (like "_Cancel"). Anyway, thanks again
Comment 10 Fernando Herrera 2004-04-15 18:00:41 UTC
We removed the Cancel confirm dialog, so closing this