268470 - Thunderbird/Firefox incorrectly assumes Control as the Accel key in input windows

Status: RESOLVED EXPIRED

(Thunderbird :: Message Compose Window, defect)

Description

[Bhroam Mann]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10.1
Build Identifier: Thunderbird .8 and .9

I changed the Accel key in both thunderbird from the default control to Meta. 
This was done by editing the prefs.js file and adding the following line:
user_pref("ui.key.accelKey", 224);

This allowed me to use several control key sequences in the edit window such as
control A to move to the front of the line and control E to move to the end.  I
also used Control U to delete a line.

Starting in Thunderbird .8 (and in .9), hitting control A in a compose window
will select all.  This is the correct behavior if control is the accel key. 
Control E does nothing as well as control U.  The home and end keys work as
expected.

The menus still list Meta as the key sequence to activate the keyboard shortcuts
and they do work.  An example is Meta M opens a new compose window while Control
M will not.

This is most annoying in thunderbird, but it also happens in firefox in input
text boxes.  I added the user_pref() line in both my firefox and thunderbird
prefs.js

Reproducible: Always
Steps to Reproduce:
1. edit prefs.js and add user_pref("ui.key.accelKey", 224);
2. start thunderbird
3. open compose window
4. type a few words and then hit Control A

Actual Results:  
The entire paragraph will be highlighted as it would with a select all

Expected Results:  
The cursor would move to the beginning of the line.

I do have several extensions installed, but this behavior happens even if they
are all disabled.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.