Working with profiles disables setting of "ui.key.accelKey"



15 years ago
13 years ago


(Reporter: Peter.Weiss, Unassigned)



Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
Build Identifier: ozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3

Working with profiles disables usability of "ui.key.accelKey" 

Reproducible: Always
Steps to Reproduce:
1. Start with rm -rf $HOME/.mozilla 
2. set user.js up with 
   user_pref("ui.key.accelKey", 18); 
   user_pref("ui.key.menuAccessKey", 0); 
3. If Mozilla starts with the default profile everything works as expected 
If Step 1a) would be: 
1a) Start mozilla -P and create a new profile (I wanted another regional section to  
      choose than the default) 
=> With same settings in user.js the settings are ignored 

Expected Results:  
Be able to handle more than one profile with 
user_pref("ui.key.accelKey", 18); 
user_pref("ui.key.menuAccessKey", 0); 

This is related to Bugs 89524,101046 
IMHO this should be mentioned in the docs somewhere. At the moment using profiles 
in conjunction with "ui.key.accelKey" is a useless thing.
Product: Browser → Seamonkey

Comment 1

14 years ago

Confirmed on Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a6) Gecko/20050215
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.