Comments on: Firefox 2 breaks numeric access keys http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/ Seeking Best Accessibility Practices Tue, 13 May 2008 04:54:10 +0000 http://wordpress.org/?v=2.1 By: Bob Easton http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-9926 Bob Easton Mon, 06 Nov 2006 02:42:34 +0000 http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-9926 Some fellow going by the name "Spud" posted a comment on Gez Lemon's article saying we're making a big fuss about nothing. The fix is simple... about:config filter on ui.key.contentAccess and set the value to 4. (was set to 5) As <a href="http://www.brucelawson.co.uk/" rel="nofollow">Bruce Lawson</a> says, "simple and intuitive." Gotta love Bruce's sense of humor. Some fellow going by the name “Spud” posted a comment on Gez Lemon’s article saying we’re making a big fuss about nothing. The fix is simple…

about:config
filter on ui.key.contentAccess and set the value to 4.
(was set to 5)

As Bruce Lawson says, “simple and intuitive.” Gotta love Bruce’s sense of humor.

]]> By: blue http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-18359 blue Fri, 22 Dec 2006 08:52:48 +0000 http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-18359 Initially I was angry about the change, but the more I read, the more it makes sense. Still, for my selfish convenient, I would rather have the old "Alt" key back. Spud's "intuitive" solution works perfectly for me. Initially I was angry about the change, but the more I read, the more it makes sense. Still, for my selfish convenient, I would rather have the old “Alt” key back. Spud’s “intuitive” solution works perfectly for me.

]]> By: Bob Easton http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-20972 Bob Easton Fri, 05 Jan 2007 14:51:23 +0000 http://www.access-matters.com/2006/11/05/firefox-2-breaks-numeric-access-keys/#comment-20972 It's fixed now. Upgrade to FF 2.0.0.1. Reset ui.key.contentAccess back to 5. It’s fixed now. Upgrade to FF 2.0.0.1. Reset ui.key.contentAccess back to 5.

]]>