Jesse has some good test cases i'd like to add (eventually) to my QA docs for keyboard navigation. here are a couple that deal with accesskeys (mnemonics), both in xul and in page-defined: bug 129808 - when focus is on category item in prefs, accesskey in panel does not move focus to the panel (need to hit tab first before accesskey will be recognized). bug 129889 - some page accesskey issues...
Status: NEW → ASSIGNED
QA Contact: endico → paw
accepting QA for mozilla developer docs. some of these bugs have been around for a _long_ time. Reporters, would you please review the bugs, see if the issues have been resolved, and close bugs appropriately. I will do a full review of all bugs not touched in one week (8th April). Thanks. </spam>
QA Contact: paw → imajes
resetting qa contact back to paul --since he's the primary person who currently reviews/verifies my testdev stuff.
QA Contact: imajes → paw
with the menu specs at a good, implemented stage, i should update accelerator (hotkey shortcuts) and accesskey (mnemonics) info to point to 'em. cross-ref in the corresponding toplevel and context menu test docs, too. toplevel browser menus: accelerators and accesskeys: http://mozilla.org/mailnews/specs/proposals/MenuFrame.html context menus for the browser: accesskeys and keybd shortcut access to bring up the context menu: http://mozilla.org/projects/ui/communicator/framework/contextmenus/
took care of comment 4 by updating http://mozilla.org/quality/browser/front-end/testcases/keyboard-nav/index.html
add refs to type-ahead find (bug 30088), ref to bug 141925, and clean up refs to xul access keys in http://www.mozilla.org/quality/browser/front-end/testcases/keyboard-nav/index.html
There doesn't seem to be anything specific left to do in this bug, is there?
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.