Bug 726119 - Two accelerators for "C" in wizard
Summary: Two accelerators for "C" in wizard
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gtk2
Version: 6.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Cosimo Cecchi
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 15:17 UTC by Michal Nowak
Modified: 2013-04-30 22:55 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-16 09:55:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Michal Nowak 2011-07-27 15:17:53 UTC 
Description of problem:

There are two accelerators for "C" in reporting wizard (_Close, _Cancel). When thinking about it... I don't understand the difference between Cancel & Close in this wizard...

Version-Release number of selected component (if applicable):

abrt-2.0.4-1.el6.x86_64
libreport-2.0.5-1.el6.x86_64
btparser-0.13-1.el6.x86_64
Comment 2 Jiri Moskovcak 2011-08-03 14:19:46 UTC 
This seems more like a bug in gtk, we don't add any additional buttons to wizard.
Comment 4 RHEL Program Management 2011-08-04 15:47:47 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 RHEL Program Management 2011-12-16 09:55:07 UTC 
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.