User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20150125221831 Steps to reproduce: 1. Open about:config 2. Set Ui.key.chromeAccess to 0 3. Restart Firefox 4. Press Alt-F, Alt-B, etc Actual results: Alt-F and Alt-B still bring up the File and Bookmarks menus, respectively. Expected results: Alt-key combinations should not bring up menus with this chromeAccess setting.
Knowledge base page on the Ui.key.chromeAccess setting: http://kb.mozillazine.org/Ui.key.chromeAccess
OSes I can confirm this on: Ubuntu 14.10 64-bit, Windows XP SP3, Windows 7 64-bit.
Just discovered that I /cannot/ reproduce this bug in the version of GNOME 3.12 that comes with Ubuntu 14.10.
If you want to disable access to the menu bar via keyboard shortcuts, you must set ui.key.menuAccessKey to 0 and restart Firefox for the change to take effect. https://hg.mozilla.org/releases/mozilla-release/annotate/458a303eebe5/modules/libpref/init/all.js#l1826
(In reply to Gingerbread Man from comment #4) > If you want to disable access to the menu bar via keyboard shortcuts, you > must set ui.key.menuAccessKey to 0 and restart Firefox for the change to > take effect. > > https://hg.mozilla.org/releases/mozilla-release/annotate/458a303eebe5/ > modules/libpref/init/all.js#l1826 ui.key.menuAccessKey is set to 0 on my system, but the bug still happens as described.
Works for me. Tested Windows 7 x64, Windows XP SP3 x86 and Linux Mint KDE x64 17.1. Firefox 36.0.4 with otherwise brand new profiles in all cases. Please retest with a fresh profile, and once again keep in mind you must restart Firefox after setting ui.key.menuAccessKey to 0. https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
I created a fresh profile, set ui.key.menuAccessKey to 0 and ui.key.chromeAccess to 0, restarted Firefox (version 37 now), and alt-F / alt-B still bring up the File and Bookmark menus, respectively.
Just discovered that setting ui.key.menuAccessKey to 0 in Windows 7 and Windows XP /does/ fix the issue, so my theory is now that the problem is specific to Ubuntu's Unity interface, given that the bug doesn't happen in KDE or GNOME. I've changed the bug's platform to "Linux"; I wish there was a way to specify desktop environment.