Bug 800821 - FF under locale cy_GB can't be quit by shortcut
Summary: FF under locale cy_GB can't be quit by shortcut
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firefox
Version: 6.2
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 10:55 UTC by Martin Simon
Modified: 2016-09-20 02:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-29 12:19:52 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 910681 0 None None None Never

Description Martin Simon 2012-03-07 10:55:25 UTC 
Description of problem:
Under locale cy_GB the quit shortcut is set to CTRL+G as well as Page Info (in cy_GB it's named "Gwybodaeth am y Dudalen") and by pressing CTRL+G the page info appear instead of quit the FF, so it's impossible to quit FF using the shortcut

Version-Release number of selected component (if applicable):
firefox-10.0.1-1.el6_2.x86_64

How reproducible:
100%

Steps to Reproduce:
1.LANG=cy_GB firefox
2.press CTRL+G to quit
3.
  
Actual results:
Window Page info appear, FF doesn't quit

Expected results:
FF quit

Additional info:
As I wrote in bz800810, maybe the shortcuts should be standardized at all, instead of fixing this bug.
Comment 2 RHEL Program Management 2012-05-03 04:56:28 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

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.
Comment 3 Martin Stransky 2013-08-29 12:19:52 UTC 
We're not going to fix it in RHEL.
Note You need to log in before you can comment on or make changes to this bug.